Bug 235183 - Saving a complete web page to an open folder crashes Dolphin
Summary: Saving a complete web page to an open folder crashes Dolphin
Status: RESOLVED DUPLICATE of bug 208921
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-23 17:03 UTC by Jonathan
Modified: 2010-04-24 20:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan 2010-04-23 17:03:24 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-20-server x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Twice, I had Dolphin open displaying an empty folder. From Firefox, I saved a complete web page, which saves an HTML file and a similarly named folder, to the folder being displayed by Dolphin. Both times, Dolphin crashed almost immediately.

I hypothesize that the creation of the file and the folder at virtually the same time caused the next directory scan by Dolphin to pick up more changes than it expected between scans, and it did not allocate enough memory to handle both changes at once. But without looking at the code, I really have absolutely no basis for this hypothesis.

To reproduce:
 1. Open an empty directory in Dolphin and let it sit there, displaying it
 2. Browse to a web page containing at least one image with Firefox (I'm running 3.5.9, if that makes any difference)
 3. Save the page to the directory open in Dolphin, with the type set to "Web Page, complete" (I saved it with a name ending in .html, but two different names besides for that)
 4. Dolphin will likely crash just after picking up the two new objects in the directory


 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f9bc0ccb249 in ?? () from /lib/libdbus-1.so.3
#6  0x00007f9bc0cac40d in ?? () from /lib/libdbus-1.so.3
#7  0x00007f9bc0cbdc8d in ?? () from /lib/libdbus-1.so.3
#8  0x00007f9bc0cafdce in ?? () from /lib/libdbus-1.so.3
#9  0x00007f9bc818d733 in q_dbus_timeout_handle (this=0x1286820, e=<value optimized out>) at ./qdbus_symbols_p.h:172
#10 QDBusConnectionPrivate::timerEvent (this=0x1286820, e=<value optimized out>) at qdbusintegrator.cpp:1023
#11 0x00007f9bc72dbd83 in QObject::event (this=0x1286820, e=0x0) at kernel/qobject.cpp:1075
#12 0x00007f9bc775fefc in QApplicationPrivate::notify_helper (this=0x1298c50, receiver=0x1286820, e=0x7fff4875a340) at kernel/qapplication.cpp:4056
#13 0x00007f9bc77671ce in QApplication::notify (this=0x7fff4875a690, receiver=0x1286820, e=0x7fff4875a340) at kernel/qapplication.cpp:4021
#14 0x00007f9bc8a94ab6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0x00007f9bc72ccc2c in QCoreApplication::notifyInternal (this=0x7fff4875a690, receiver=0x1286820, event=0x7fff4875a340) at kernel/qcoreapplication.cpp:610
#16 0x00007f9bc72f7862 in QCoreApplication::sendEvent (this=0x129c460) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 QTimerInfoList::activateTimers (this=0x129c460) at kernel/qeventdispatcher_unix.cpp:572
#18 0x00007f9bc72f525d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#19 0x00007f9bc2debbce in g_main_dispatch (context=0x129b520) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x129b520) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#21 0x00007f9bc2def598 in g_main_context_iterate (context=0x129b520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#22 0x00007f9bc2def6c0 in IA__g_main_context_iteration (context=0x129b520, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#23 0x00007f9bc72f51a6 in QEventDispatcherGlib::processEvents (this=0x126bd20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#24 0x00007f9bc77f44be in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f9bc72cb532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#26 0x00007f9bc72cb904 in QEventLoop::exec (this=0x7fff4875a5e0, flags=) at kernel/qeventloop.cpp:201
#27 0x00007f9bc72cdab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000439555 in _start ()

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-04-24 20:15:29 UTC
This bug is fixed in KDE 4.3.5 and later. Thanks for reporting!

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