Bug 277438 - Konqueror crashes by closing it
Summary: Konqueror crashes by closing it
Status: RESOLVED DUPLICATE of bug 231265
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-09 21:42 UTC by Gatoso
Modified: 2011-07-10 10:36 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 Gatoso 2011-07-09 21:42:16 UTC
Application: konqueror (4.6.5 (4.6.5))
KDE Platform Version: 4.6.5 (4.6.5) (Compiled from sources)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-pae i686
Distribution (Platform): Archlinux Packages

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

Same behaviour of Konqueror (I think since KDE 4.6.3). When I close the program, it crashes. No matter what web page I have open (or how many of these), always crashes.

- Unusual behavior I noticed:

-- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5577b60 (LWP 1513))]

Thread 4 (Thread 0xa474bb70 (LWP 1532)):
#0  0xb76e4424 in __kernel_vsyscall ()
#1  0xb6bdacd3 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xa8f5ca39 in metronom_sync_loop () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 3 (Thread 0xa992cb70 (LWP 2679)):
#0  0xb76e4424 in __kernel_vsyscall ()
#1  0xb6bda92b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb327c361 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0xb33816c0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#3  0xb327c39f in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0xb33816c0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#4  0xb6bd6cb7 in start_thread () from /lib/libpthread.so.0
#5  0xb5ee8e7e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xaa92eb70 (LWP 2790)):
#0  0xb76e4424 in __kernel_vsyscall ()
#1  0xb6bda92b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb411aa81 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/libQtWebKit.so.4
#3  0xb411aabf in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/libQtWebKit.so.4
#4  0xb6bd6cb7 in start_thread () from /lib/libpthread.so.0
#5  0xb5ee8e7e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5577b60 (LWP 1513)):
[KCrash Handler]
#7  0x00000018 in ?? ()
#8  0xb6d65738 in QMetaObject::cast (this=0xb49d7510, obj=0xb639188) at kernel/qmetaobject.cpp:266
#9  0xad7f3588 in qobject_cast<KParts::ReadWritePart*> (object=0xb639188) at /usr/include/QtCore/qobject.h:366
#10 0xad7f0039 in SearchBarPlugin::updateComboVisibility (this=0x88a31c0) at /home/zuargo/Paquetes/konq-plugins/src/konq-plugins-4.6.1/searchbar/searchbar.cpp:424
#11 0xad7f1fa3 in SearchBarPlugin::qt_metacall (this=0x88a31c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x19f4a578) at /home/zuargo/Paquetes/konq-plugins/src/build/searchbar/searchbar.moc:193
#12 0xb6d65714 in metacall (object=0x88a31c0, cl=QMetaObject::InvokeMetaMethod, idx=12, argv=0x19f4a578) at kernel/qmetaobject.cpp:237
#13 QMetaObject::metacall (object=0x88a31c0, cl=QMetaObject::InvokeMetaMethod, idx=12, argv=0x19f4a578) at kernel/qmetaobject.cpp:232
#14 0xb6d71175 in QMetaCallEvent::placeMetaCall (this=0x12a72790, object=0x88a31c0) at kernel/qobject.cpp:535
#15 0xb6d7a152 in QObject::event (this=0x88a31c0, e=0x12a72790) at kernel/qobject.cpp:1217
#16 0xb61a1c4c in notify_helper (this=0x88054f0, receiver=0x88a31c0, e=0x12a72790) at kernel/qapplication.cpp:4462
#17 QApplicationPrivate::notify_helper (this=0x88054f0, receiver=0x88a31c0, e=0x12a72790) at kernel/qapplication.cpp:4434
#18 0xb61a7df0 in QApplication::notify (this=0x88054f0, receiver=0x88a31c0, e=0x12a72790) at kernel/qapplication.cpp:4341
#19 0xb747f321 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0xb6d5e50e in QCoreApplication::notifyInternal (this=0xbf8710c8, receiver=0x88a31c0, event=0x12a72790) at kernel/qcoreapplication.cpp:731
#21 0xb6d627e8 in sendEvent (receiver=0x0, event_type=0, data=0x873f6d8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x873f6d8) at kernel/qcoreapplication.cpp:1372
#23 0xb6d62a3c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1265
#24 0xb6d90f94 in sendPostedEvents (s=0x8806da8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#25 postEventSourceDispatch (s=0x8806da8) at kernel/qeventdispatcher_glib.cpp:277
#26 0xb594aa1f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb594b198 in g_main_context_iterate.isra.19 () from /usr/lib/libglib-2.0.so.0
#28 0xb594b4da in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb6d9146a in QEventDispatcherGlib::processEvents (this=0x87de0a8, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#30 0xb6265a1a in QGuiEventDispatcherGlib::processEvents (this=0x87de0a8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0xb6d5cbbd in QEventLoop::processEvents (this=0xbf870fb4, flags=...) at kernel/qeventloop.cpp:149
#32 0xb6d5ce09 in QEventLoop::exec (this=0xbf870fb4, flags=...) at kernel/qeventloop.cpp:201
#33 0xb6d62aed in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#34 0xb619fa14 in QApplication::exec () at kernel/qapplication.cpp:3736
#35 0xb07204a9 in kdemain (argc=4, argv=0x87da228) at /home/zuargo/Paquetes/kdebase/src/kdebase-4.6.5/konqueror/src/konqmain.cpp:219
#36 0x0804f24a in _start ()

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

Possible duplicates by query: bug 268429, bug 265936, bug 265927.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2011-07-10 10:36:25 UTC
Caused by the Search Bar Plugin - disable it to work around this crash.

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