Bug 262703 - Konqueror was in the background when crash occured.
Summary: Konqueror was in the background when crash occured.
Status: RESOLVED DUPLICATE of bug 264526
Alias: None
Product: konqueror
Classification: Applications
Component: kjs (show other bugs)
Version: 4.6.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 262791 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-09 22:44 UTC by m.wege
Modified: 2012-06-18 21:24 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 m.wege 2011-01-09 22:44:32 UTC
Application: konqueror (4.5.95 (4.6 RC2))
KDE Platform Version: 4.5.95 (4.6 RC2)
Qt Version: 4.7.0
Operating System: Linux 2.6.37-11-generic-pae i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed: Konqueror was in the background when crash occured.. Konqueror was in the background when crash occured.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4e1f710 (LWP 6480))]

Thread 2 (Thread 0xae9b2b70 (LWP 8855)):
#0  0xb5529e36 in clock_gettime () from /lib/librt.so.1
#1  0xb678e50b in do_gettime () at tools/qelapsedtimer_unix.cpp:105
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:119
#3  0xb68656e5 in QTimerInfoList::updateCurrentTime (this=0xbaca7e4) at kernel/qeventdispatcher_unix.cpp:339
#4  0xb686572a in QTimerInfoList::timerWait (this=0xbaca7e4, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0xb68637a8 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xae9b20bc) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb686383d in timerSourcePrepare (source=0x0, timeout=0xb552dff4) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb5496e6a in g_main_context_prepare () from /lib/libglib-2.0.so.0
#8  0xb5497279 in ?? () from /lib/libglib-2.0.so.0
#9  0xb5497848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#10 0xb686359f in QEventDispatcherGlib::processEvents (this=0xe103ee0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#11 0xb6833609 in QEventLoop::processEvents (this=0xae9b2290, flags=) at kernel/qeventloop.cpp:149
#12 0xb6833a8a in QEventLoop::exec (this=0xae9b2290, flags=...) at kernel/qeventloop.cpp:201
#13 0xb672fb7e in QThread::exec (this=0xde20770) at thread/qthread.cpp:490
#14 0xb681235b in QInotifyFileSystemWatcherEngine::run (this=0xde20770) at io/qfilesystemwatcher_inotify.cpp:248
#15 0xb6732df9 in QThreadPrivate::start (arg=0xde20770) at thread/qthread_unix.cpp:266
#16 0xb5539cc9 in start_thread () from /lib/libpthread.so.0
#17 0xb762869e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4e1f710 (LWP 6480)):
[KCrash Handler]
#7  0xb1fb6bbc in type (exec=0x192875d0, ctx=0x192875c0, in=0xb263a260, path=...) at ../../kjs/value.h:452
#8  KJS::cloneInternal (exec=0x192875d0, ctx=0x192875c0, in=0xb263a260, path=...) at ../../khtml/ecma/kjs_data.cpp:37
#9  0xb1fb7054 in KJS::encapsulateMessageEventData (exec=0x192875d0, ctx=0x192875c0, data=0xb263a260) at ../../khtml/ecma/kjs_data.cpp:117
#10 0xb1fb7256 in KJS::DelayedPostMessage::execute (this=0x1c0105b8, w=0xaf4d08c0) at ../../khtml/ecma/kjs_data.cpp:169
#11 0xb1f59bab in KJS::Window::afterScriptExecution (this=0xaf4d08c0) at ../../khtml/ecma/kjs_window.cpp:1327
#12 0xb1f5b4ef in KJS::WindowQObject::timerEvent (this=0x17e20350) at ../../khtml/ecma/kjs_window.cpp:2481
#13 0xb6847504 in QObject::event (this=0x17e20350, e=0xb263a260) at kernel/qobject.cpp:1183
#14 0xb5cb7fdc in QApplicationPrivate::notify_helper (this=0x99c2b18, receiver=0x17e20350, e=0xbf902fd0) at kernel/qapplication.cpp:4396
#15 0xb5cbe04e in QApplication::notify (this=0xbf903454, receiver=0x17e20350, e=0xbf902fd0) at kernel/qapplication.cpp:3798
#16 0xb6e19f8a in KApplication::notify (this=0xbf903454, receiver=0x17e20350, event=0xbf902fd0) at ../../kdeui/kernel/kapplication.cpp:311
#17 0xb6834b3b in QCoreApplication::notifyInternal (this=0xbf903454, receiver=0x17e20350, event=0xbf902fd0) at kernel/qcoreapplication.cpp:732
#18 0xb6866ad6 in sendEvent (this=0x99c5d34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x99c5d34) at kernel/qeventdispatcher_unix.cpp:602
#20 0xb68638a7 in timerSourceDispatch (source=0x99c5898) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=0x99c5898) at kernel/qeventdispatcher_glib.cpp:231
#22 0xb5493855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0xb5497668 in ?? () from /lib/libglib-2.0.so.0
#24 0xb5497848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0xb6863565 in QEventDispatcherGlib::processEvents (this=0x99c2af8, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#26 0xb5d79be5 in QGuiEventDispatcherGlib::processEvents (this=0x99c2af8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0xb6833609 in QEventLoop::processEvents (this=0xbf903294, flags=) at kernel/qeventloop.cpp:149
#28 0xb6833a8a in QEventLoop::exec (this=0xbf903294, flags=...) at kernel/qeventloop.cpp:201
#29 0xb683800f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#30 0xb5cb6e07 in QApplication::exec () at kernel/qapplication.cpp:3672
#31 0xb7793e42 in kdemain (argc=3, argv=0xbf903734) at ../../../../apps/konqueror/src/konqmain.cpp:234
#32 0x080485ab in main (argc=3, argv=0xbf903734) at konqueror_dummy.cpp:3

This bug may be a duplicate of or related to bug 261403.

Possible duplicates by query: bug 261403.

Reported using DrKonqi
Comment 1 Tommi Tervo 2011-01-10 21:48:17 UTC
*** Bug 262791 has been marked as a duplicate of this bug. ***
Comment 2 Dario Andres 2011-02-20 00:00:08 UTC
[Comment from a bug triager]
The backtrace looks similar to the one in bug 264526. Do you remember if the situation was similar (chat on facebook) ?
Regards
Comment 3 Myriam Schweingruber 2012-06-18 21:24:07 UTC

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