Bug 290555

Summary: Konq crash during normal browsing (No facebook)
Product: [Applications] konqueror Reporter: David <davidsboogs>
Component: khtml ecmaAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: dglent, dilnix, frolvlad, gabrimonfa, kevin, kollix, madmikehooper, mzpc, sergeygraf.rus
Priority: NOR    
Version: 4.7.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi
New crash information added by DrKonqi

Description David 2012-01-04 02:12:10 UTC
Application: konqueror (4.7.4 (4.7.4))
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-14-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

This is perhaps the second instance I've seen where Konqueror just crashes, but the backtraces don't look similar to me (the other is bug 290306 )

I was doing normal browsing, but unlike most of the duplicates DrKonqi suggests, I was not on facebook at all.  I may or may not have just closed a tab, but in any case had just switched to a different one.  I currently forget what I was searching for (I typically use Konq for quick web searches) but it might tell me when I relaunch after filing this.

Kubuntu 11.10 amd64 using KDE 4.7.4 from the Kubuntu PPA.

Please let me know if there is any more info I could supply.

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

Thread 2 (Thread 0x7fe36ec06700 (LWP 11035)):
#0  0x00007fe384ff9034 in __pthread_mutex_lock (mutex=0x1f7e798) at pthread_mutex_lock.c:61
#1  0x00007fe38472cf2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe38472d429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe389425f3e in QEventDispatcherGlib::processEvents (this=0x1d58a00, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fe3893f9cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fe3893f9ef7 in QEventLoop::exec (this=0x7fe36ec05dd0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fe38931127f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007fe3893dccbf in QInotifyFileSystemWatcherEngine::run (this=0x1f7dbf0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fe389313d05 in QThreadPrivate::start (arg=0x1f7dbf0) at thread/qthread_unix.cpp:331
#9  0x00007fe384ff6efc in start_thread (arg=0x7fe36ec06700) at pthread_create.c:304
#10 0x00007fe38b8fe89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe38c07f780 (LWP 10987)):
[KCrash Handler]
#6  0x00007fe3791b72ca in type (this=0x7fe36a32be80) at ../../kjs/value.h:452
#7  KJS::cloneInternal (exec=0x238fec0, ctx=0x238fea0, in=0x7fe36a32be80, path=...) at ../../khtml/ecma/kjs_data.cpp:37
#8  0x00007fe3791b7763 in KJS::encapsulateMessageEventData (exec=0x238fec0, ctx=<optimized out>, data=<optimized out>) at ../../khtml/ecma/kjs_data.cpp:117
#9  0x00007fe3791b7955 in KJS::DelayedPostMessage::execute (this=0x49ce040, w=<optimized out>) at ../../khtml/ecma/kjs_data.cpp:169
#10 0x00007fe37916cc8b in KJS::Window::afterScriptExecution (this=0x7fe36e350080) at ../../khtml/ecma/kjs_window.cpp:1327
#11 0x00007fe379173d1e in KJS::WindowQObject::timerEvent (this=0x3069ff0) at ../../khtml/ecma/kjs_window.cpp:2481
#12 0x00007fe389411789 in QObject::event (this=0x3069ff0, e=<optimized out>) at kernel/qobject.cpp:1181
#13 0x00007fe388532424 in notify_helper (e=0x7fff19c67870, receiver=0x3069ff0, this=0x181a3a0) at kernel/qapplication.cpp:4486
#14 QApplicationPrivate::notify_helper (this=0x181a3a0, receiver=0x3069ff0, e=0x7fff19c67870) at kernel/qapplication.cpp:4458
#15 0x00007fe388537291 in QApplication::notify (this=0x7fff19c67cd0, receiver=0x3069ff0, e=0x7fff19c67870) at kernel/qapplication.cpp:4365
#16 0x00007fe389e30466 in KApplication::notify (this=0x7fff19c67cd0, receiver=0x3069ff0, event=0x7fff19c67870) at ../../kdeui/kernel/kapplication.cpp:311
#17 0x00007fe3893faafc in QCoreApplication::notifyInternal (this=0x7fff19c67cd0, receiver=0x3069ff0, event=0x7fff19c67870) at kernel/qcoreapplication.cpp:787
#18 0x00007fe389427d62 in sendEvent (event=0x7fff19c67870, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x181c3a0) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007fe389425538 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#22 0x00007fe38472ca5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fe38472d258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007fe38472d429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007fe389425ed6 in QEventDispatcherGlib::processEvents (this=0x17f2fa0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#26 0x00007fe3885da07e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00007fe3893f9cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#28 0x00007fe3893f9ef7 in QEventLoop::exec (this=0x7fff19c67b00, flags=...) at kernel/qeventloop.cpp:201
#29 0x00007fe3893fe789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#30 0x00007fe38bc72a8a in kdemain (argc=<optimized out>, argv=<optimized out>) at ../../../konqueror/src/konqmain.cpp:242
#31 0x00007fe38b83e30d in __libc_start_main (main=0x400640 <main(int, char**)>, argc=2, ubp_av=0x7fff19c68688, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff19c68678) at libc-start.c:226
#32 0x0000000000400671 in _start ()

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

Possible duplicates by query: bug 290222, bug 285648, bug 284590, bug 281325, bug 278507.

Reported using DrKonqi
Comment 1 David 2012-01-04 02:21:43 UTC
At the time of the crash I was looking for how to do something in the Android app "Any.DO" the tabs open were:

Google search:
http://www.google.com/search?q=android+%22any.do%22+support&client=ubuntu&channel=ks&gs_sm=e&gs_upl=6054l6944l0l7138l2l2l0l0l0l0l284l400l0.1.1l2l0&oq=android+%22any.do%22+support&aq=f&aqi=&aql=

The app's Android market page:
https://market.android.com/details?id=com.anydo&hl=en

******** Here's the bonus ********
After restoring the session, around half a minute later (but after the pages have been loaded for a while) it crashes again!
It's the android market page that does it, including in a fresh window, so we have a consistant repro!
Comment 2 David 2012-01-04 02:31:05 UTC
That market page does not crash rekonq (nor of course Chrome, nor Firefox), just Konqueror.
Comment 3 Martin Koller 2012-01-05 14:18:51 UTC
The crash still happens with 4.8.rc2 with the same stack
Comment 4 Martin Koller 2012-01-05 18:59:01 UTC
*** Bug 290222 has been marked as a duplicate of this bug. ***
Comment 5 Dawit Alemayehu 2012-01-27 18:42:38 UTC
(In reply to comment #2)
> That market page does not crash rekonq (nor of course Chrome, nor Firefox),
> just Konqueror.

This is a khtml specific crash. Not a Konqueror crash. There is a big distinction because Konqueror comes with two separate browser engines, khtml and webkit.
Comment 6 Tommi Tervo 2012-01-31 19:39:21 UTC
*** Bug 292992 has been marked as a duplicate of this bug. ***
Comment 7 Jekyll Wu 2012-02-25 09:34:10 UTC
*** Bug 294794 has been marked as a duplicate of this bug. ***
Comment 8 Jekyll Wu 2012-03-26 12:36:30 UTC
*** Bug 296811 has been marked as a duplicate of this bug. ***
Comment 9 Dimitrios Glentadakis 2012-03-27 16:16:28 UTC
Created attachment 69940 [details]
New crash information added by DrKonqi

konqueror (4.6.5 (4.6.5)) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.4

I visited the page:
https://play.google.com/store/apps/details?id=com.orange.labs.whoscalling&feature=order_history

and konqueror crashs (twice, in three tentatives)

-- Backtrace (Reduced):
#6  0x00007f07061df7fa in type (exec=0x651a670, ctx=0x651a650, in=0x7f06f8aa3e80, path=...) at /usr/src/debug/kdelibs-4.6.5/kjs/value.h:452
#7  KJS::cloneInternal (exec=0x651a670, ctx=0x651a650, in=0x7f06f8aa3e80, path=...) at /usr/src/debug/kdelibs-4.6.5/khtml/ecma/kjs_data.cpp:37
#8  0x00007f07061dfbf0 in KJS::encapsulateMessageEventData (exec=0x651a670, ctx=<value optimized out>, data=<value optimized out>) at /usr/src/debug/kdelibs-4.6.5/khtml/ecma/kjs_data.cpp:117
#9  0x00007f07061dfe06 in KJS::DelayedPostMessage::execute (this=0xb439c70, w=<value optimized out>) at /usr/src/debug/kdelibs-4.6.5/khtml/ecma/kjs_data.cpp:169
#10 0x00007f0706192fd3 in KJS::Window::afterScriptExecution (this=0x7f0701f70200) at /usr/src/debug/kdelibs-4.6.5/khtml/ecma/kjs_window.cpp:1327
Comment 10 Jekyll Wu 2012-03-29 16:22:01 UTC
*** Bug 297056 has been marked as a duplicate of this bug. ***
Comment 11 Andrea Iacovitti 2012-04-15 09:09:03 UTC
*** Bug 298041 has been marked as a duplicate of this bug. ***
Comment 12 bostaurus 2012-04-17 15:34:32 UTC
Created attachment 70453 [details]
New crash information added by DrKonqi

konqueror (4.8.2 (4.8.2)) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed: I tried to login into my email-account www.web.de. Konqueror crashed at once.

-- Backtrace (Reduced):
#7  0xb03174a4 in type (this=0xaf057880) at ../../kjs/value.h:452
#8  KJS::cloneInternal (exec=0x9ac9698, ctx=0x9ac9688, in=0xaf057880, path=...) at ../../khtml/ecma/kjs_data.cpp:37
#9  0xb03179bd in KJS::encapsulateMessageEventData (exec=0x9ac9698, ctx=0x9ac9688, data=0xaf057880) at ../../khtml/ecma/kjs_data.cpp:117
#10 0xb0317bab in KJS::DelayedPostMessage::execute (this=0xb0619d0, w=0x0) at ../../khtml/ecma/kjs_data.cpp:169
#11 0xb02c64d4 in KJS::Window::afterScriptExecution (this=0xaf100040) at ../../khtml/ecma/kjs_window.cpp:1327
Comment 13 dilnix 2012-05-08 06:00:31 UTC
Created attachment 70941 [details]
New crash information added by DrKonqi

akregator (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

- What I was doing when the application crashed:
Just switched to full article link (http://ozz.tv/serial/31), Akregator opened it for a second and crash. This all done on freshly booted system. No other browsing app was launched.

-- Backtrace (Reduced):
#7  0x46ca0651 in type (this=0xb3979f40) at /usr/src/debug/kdelibs-4.8.3/kjs/value.h:452
#8  KJS::cloneInternal (exec=exec@entry=0xa864a58, ctx=ctx@entry=0xa864a48, in=in@entry=0xb3979f40, path=...) at /usr/src/debug/kdelibs-4.8.3/khtml/ecma/kjs_data.cpp:37
#9  0x46ca0a3e in KJS::encapsulateMessageEventData (exec=0xa864a58, ctx=0xa864a48, data=0xb3979f40) at /usr/src/debug/kdelibs-4.8.3/khtml/ecma/kjs_data.cpp:117
#10 0x46ca0c3b in KJS::DelayedPostMessage::execute (this=0xa98e768, w=0x0) at /usr/src/debug/kdelibs-4.8.3/khtml/ecma/kjs_data.cpp:169
#11 0x46c4fef4 in KJS::Window::afterScriptExecution (this=0xb44f0000) at /usr/src/debug/kdelibs-4.8.3/khtml/ecma/kjs_window.cpp:1327
Comment 14 Vlad 2012-05-08 15:11:25 UTC
Created attachment 70955 [details]
New crash information added by DrKonqi

akregator (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

I switched opened pages tabs in Akregator. This crash happens sometimes.

-- Backtrace (Reduced):
#7  0xb51314a4 in type (this=0xb0cbb160) at ../../kjs/value.h:452
#8  KJS::cloneInternal (exec=0xa5706d0, ctx=0xa5706c0, in=0xb0cbb160, path=...) at ../../khtml/ecma/kjs_data.cpp:37
#9  0xb51319bd in KJS::encapsulateMessageEventData (exec=0xa5706d0, ctx=0xa5706c0, data=0xb0cbb160) at ../../khtml/ecma/kjs_data.cpp:117
#10 0xb5131bab in KJS::DelayedPostMessage::execute (this=0x1064d960, w=0x0) at ../../khtml/ecma/kjs_data.cpp:169
#11 0xb50e04d4 in KJS::Window::afterScriptExecution (this=0xab5303c0) at ../../khtml/ecma/kjs_window.cpp:1327
Comment 15 Vlad 2012-05-09 11:20:08 UTC
Created attachment 70975 [details]
New crash information added by DrKonqi

akregator (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

Yesterday I have reported that crash happens sometimes after tab switching, but today Akregator have crashed just I have reading.

-- Backtrace (Reduced):
#7  0xb51d54a4 in type (this=0xa8da19a0) at ../../kjs/value.h:452
#8  KJS::cloneInternal (exec=0xb8e5690, ctx=0xb8e5680, in=0xa8da19a0, path=...) at ../../khtml/ecma/kjs_data.cpp:37
#9  0xb51d59bd in KJS::encapsulateMessageEventData (exec=0xb8e5690, ctx=0xb8e5680, data=0xa8da19a0) at ../../khtml/ecma/kjs_data.cpp:117
#10 0xb51d5bab in KJS::DelayedPostMessage::execute (this=0x123897d0, w=0x0) at ../../khtml/ecma/kjs_data.cpp:169
#11 0xb51844d4 in KJS::Window::afterScriptExecution (this=0xacc90000) at ../../khtml/ecma/kjs_window.cpp:1327
Comment 16 Myriam Schweingruber 2012-06-18 21:23:10 UTC

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