Bug 243049 - Kolourpaint randomly crashed when I zoomed out on a png
Summary: Kolourpaint randomly crashed when I zoomed out on a png
Status: RESOLVED DUPLICATE of bug 237936
Alias: None
Product: kolourpaint
Classification: Applications
Component: general-kde4 (show other bugs)
Version: Comes with KDE
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kolourpaint-support
Depends on:
Reported: 2010-06-28 17:27 UTC by ariel.bys
Modified: 2010-08-02 02:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description ariel.bys 2010-06-28 17:27:37 UTC
Version:           Comes with KDE (using KDE 4.4.4) 
OS:                Linux

Well, when I zoomed on out on a world map .png in diplomacy, KolourPaint decided to crash. 

Application: KolourPaint (kolourpaint), signal: Aborted
[KCrash Handler]
#7  0xb7731424 in __kernel_vsyscall ()
#8  0xb5b25751 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0xb5b28b82 in *__GI_abort () at abort.c:92
#10 0xb5d4655f in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#11 0xb5d44425 in ?? () from /usr/lib/libstdc++.so.6
#12 0xb5d44462 in std::terminate() () from /usr/lib/libstdc++.so.6
#13 0xb5d445a1 in __cxa_throw () from /usr/lib/libstdc++.so.6
#14 0xb68857e5 in qBadAlloc() () from /usr/lib/libQtCore.so.4
#15 0xb5fe3c74 in QX11PixmapData::toImage() const () from /usr/lib/libQtGui.so.4
#16 0xb5fc8ccb in QPixmap::toImage() const () from /usr/lib/libQtGui.so.4
#17 0xb609689c in ?? () from /usr/lib/libQtGui.so.4
#18 0xb6096bb7 in QRegion::QRegion(QBitmap const&) () from /usr/lib/libQtGui.so.4
#19 0xb5f2eb19 in QWidget::setMask(QBitmap const&) () from /usr/lib/libQtGui.so.4
#20 0x080996c2 in _start ()

Also, I happened to run KP from a terminal. Just before crashing (like ~1 second), the terminal chunked a hairball which I describe in http://pastebin.com/AMJicmRH.

Reproducible: Didn't try
Comment 1 Christoph Feck 2010-08-02 02:25:25 UTC

*** This bug has been marked as a duplicate of bug 237936 ***