Bug 156839 - Crashed(SIGSEGV) when opening a png file.
Summary: Crashed(SIGSEGV) when opening a png file.
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 1.6.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2008-01-28 09:13 UTC by Raúl
Modified: 2008-10-26 20:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Png image tried to load. (122.89 KB, image/png)
2008-01-28 09:13 UTC, Raúl
Details
Valgrind log. Not reproduced. (34.95 KB, text/x-csrc)
2008-01-28 09:22 UTC, Raúl
Details
kritarc file. (2.38 KB, text/plain)
2008-01-29 23:37 UTC, Raúl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raúl 2008-01-28 09:13:05 UTC
Version:           1.6.3 (using 3.5.8, Debian Package 4:3.5.8.dfsg.1-6 (lenny/sid))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.24-rtoi-rc5

I started krite, created a new 1024x768 transparent image using RGB. Then I tried to load a png file using the recent list and krita crashed with SIGSEGV. See BT below.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b8c96a1f780 (LWP 4105)]
[KCrash handler]
#5  0x0000000000d14af7 in ?? ()
#6  0x00002b8c91bff38b in qt_inheritedBy (superClass=0x2aaaac419630, 
    object=0xc7f650) at kernel/qobject.cpp:596
#7  0x00002b8c91b967a7 in qt_cast<QToolBar*> (object=0xc7f650)
    at ../include/qobjectdefs.h:173
#8  0x00002b8c91d0beb3 in QMainWindow::toolBars (this=0x2aaaac3e8350, 
    dock=Qt::DockTornOff) at widgets/qmainwindow.cpp:1923
#9  0x00002b8c92b532df in KMainWindow::toolBarIterator (this=0x2aaaac3e8350)
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kdeui/kmainwindow.cpp:1161
#10 0x00002b8c92bf9623 in KMainWindow::saveMainWindowSettings (
    this=0x2aaaac3e8350, config=0x6ba120, configGroup=@0x2aaaac3f2028)
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kdeui/kmainwindow.cpp:750
#11 0x00002b8c92bf99f3 in KMainWindow::saveAutoSaveSettings (
    this=0x2aaaac3e8350)
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kdeui/kmainwindow.cpp:1053
#12 0x00002b8c92c474da in KMainWindow::qt_invoke (this=0x2aaaac3e8350, 
    _id=71, _o=0x7fff1ad0c0b0) at ./kmainwindow.moc:138
#13 0x00002b8c8fffc403 in KParts::MainWindow::qt_invoke (this=0x2aaaac3e8350, 
    _id=71, _o=0x7fff1ad0c0b0) at ./mainwindow.moc:98
#14 0x00002b8c96f273d7 in KoMainWindow::qt_invoke (this=0x2aaaac3e8350, 
    _id=71, _o=0x7fff1ad0c0b0) at ./KoMainWindow.moc:204
#15 0x00002b8c91c02186 in QObject::activate_signal (this=0x2aaaac695520, 
    clist=0x2aaaac695580, o=0x7fff1ad0c0b0) at kernel/qobject.cpp:2356
#16 0x00002b8c91c02d04 in QObject::activate_signal (this=0x2aaaac695520, 
    signal=2) at kernel/qobject.cpp:2325
#17 0x00002b8c91f7c11a in QTimer::timeout (this=0x2aaaac695520)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#18 0x00002b8c91c27fab in QTimer::event (this=0x2aaaac695520, 
    e=0x7fff1ad0c580) at kernel/qtimer.cpp:219
#19 0x00002b8c91b9a3aa in QApplication::internalNotify (this=0x7fff1ad0c940, 
    receiver=0x2aaaac695520, e=0x7fff1ad0c580) at kernel/qapplication.cpp:2635
#20 0x00002b8c91b9c158 in QApplication::notify (this=0x7fff1ad0c940, 
    receiver=0x2aaaac695520, e=0x7fff1ad0c580) at kernel/qapplication.cpp:2358
#21 0x00002b8c914fcaad in KApplication::notify (this=0x7fff1ad0c940, 
    receiver=0x2aaaac695520, event=0x7fff1ad0c580)
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kdecore/kapplication.cpp:550
#22 0x00002b8c91b2babe in QApplication::sendEvent (receiver=0x2aaaac695520, 
    event=0x7fff1ad0c580) at ../include/qapplication.h:520
#23 0x00002b8c91b8db04 in QEventLoop::activateTimers (this=0x6b91b0)
    at kernel/qeventloop_unix.cpp:556
#24 0x00002b8c91b40185 in QEventLoop::processEvents (this=0x6b91b0, flags=4)
    at kernel/qeventloop_x11.cpp:389
#25 0x00002b8c91bb4673 in QEventLoop::enterLoop (this=0x6b91b0)
    at kernel/qeventloop.cpp:198
#26 0x00002b8c91bb435f in QEventLoop::exec (this=0x6b91b0)
    at kernel/qeventloop.cpp:145
#27 0x00002b8c91b9be8c in QApplication::exec (this=0x7fff1ad0c940)
    at kernel/qapplication.cpp:2758
#28 0x00002b8c96c3d1b9 in kdemain (argc=<value optimized out>, argv=0x6438c0)
    at /tmp/buildd/koffice-1.6.3/./krita/main.cc:41
#29 0x0000000000407f68 in launch (argc=1, _name=0x653ad8 "krita", 
    args=0x653ade "\001", cwd=0x0, envc=1, envs=0x653af2 "", reset_env=false, 
    tty=0x0, avoid_loops=false, 
    startup_id_str=0x653afb "portaka;1201507441;555922;7916_TIME105227450")
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kinit/kinit.cpp:673
#30 0x0000000000408701 in handle_launcher_request (sock=11)
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kinit/kinit.cpp:1240
#31 0x0000000000408c2c in handle_requests (waitForPid=0)
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kinit/kinit.cpp:1443
#32 0x0000000000409582 in main (argc=5, argv=<value optimized out>, 
    envp=0x7fff1ad0d4e8)
    at /tmp/buildd/kdelibs-3.5.8.dfsg.1/./kinit/kinit.cpp:1908
#33 0x00002b8c909d51c4 in __libc_start_main () from /lib/libc.so.6
#34 0x0000000000404dc9 in _start ()


In the .xsession-errors I could read:
QPainter::begin: Cannot paint null pixmap
QLayout "unnamed" added to QWidget "unnamed", which already has a layout
KCrash: Application 'krita' crashing...
Comment 1 Raúl 2008-01-28 09:13:49 UTC
Created attachment 23327 [details]
Png image tried to load.
Comment 2 Cyrille Berger 2008-01-28 09:18:27 UTC
Hi,
I can't reproduce :/ The backtrace show something deep into Qt.
A few questions :
* Is the crash reproductible ?
* Does it happen when loading the file using the file dialog of "Open Existing Document" ?
* Does it happen for other png files ?
Comment 3 Raúl 2008-01-28 09:22:49 UTC
Created attachment 23328 [details]
Valgrind log. Not reproduced.

I tried getting a proper valgrind log of the crash, but I couldn't reproduce
the problem.
Comment 4 Raúl 2008-01-28 09:27:41 UTC
*It is 100% reproducible when running without valgrind.
*I don't know exactly which option you mention but once I created the transparent blank file and I could see it I chose: File->Open recent->preview.png
*Haven't tried yet.

Thanks for the fast response.
Comment 5 Cyrille Berger 2008-01-28 09:52:15 UTC
The valgrind output shows a lot of horrible things, but still nothing related to png loading :/
For the second question I either meant using the file menu open "File > open...", or the button on the bottom left labeled "Open Existing Document"
Comment 6 Raúl 2008-01-29 23:37:21 UTC
Created attachment 23357 [details]
kritarc file.

Well now we know some more clues. If I remove the kritarc file and retry I the
crash is gone.

I'm attaching my kritarc in case it is helpful to catch this ugly bug.
Comment 7 Elián Hanisch 2008-10-26 18:13:53 UTC
I can't reproduce on krita2 beta2 nor 1.6.3, either by using attached kritarc
Comment 8 Halla Rempt 2008-10-26 18:59:17 UTC
Indeed no crash here (something strange happening to my dockers, but no crash!)