Bug 218141 - KMail crashes when collapsing all the items/messages [KMail::MessageListView::Core::View::setAllThreadsExpanded, KMail::MessageListView::Pane::setAllThreadsExpanded, KMMainWidget::slotCollapseAllThreads]
Summary: KMail crashes when collapsing all the items/messages [KMail::MessageListView:...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: new message list (show other bugs)
Version: 1.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-10 18:50 UTC by pp.f.
Modified: 2012-08-19 11:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description pp.f. 2009-12-10 18:50:18 UTC 
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic-pae i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb0e4aede in KMail::MessageListView::Core::View::setAllThreadsExpanded (this=0xa21a198, expand=false) at ../../kmail/messagelistview/core/view.cpp:909
#7  0xb0dea952 in KMail::MessageListView::Pane::setAllThreadsExpanded (this=0xa1b6128, expand=false) at ../../kmail/messagelistview/pane.cpp:659
#8  0xb0c8ebca in KMMainWidget::slotCollapseAllThreads (this=0x9ac42f8) at ../../kmail/kmmainwidget.cpp:4226
#9  0xb0cb54b5 in KMMainWidget::qt_metacall (this=0x9ac42f8, _c=QMetaObject::InvokeMetaMethod, _id=88, _a=0xbfcfc0c8) at ./kmmainwidget.moc:436
#10 0xb6640263 in QMetaObject::activate (sender=0x9c7e1d0, from_signal_index=5, to_signal_index=6, argv=0xbfcfc0c8) at kernel/qobject.cpp:3113
#11 0xb66406d8 in QMetaObject::activate (sender=0x9c7e1d0, m=0xb72e8e48, from_local_signal_index=1, to_local_signal_index=2, argv=0xbfcfc0c8) at kernel/qobject.cpp:3207
#12 0xb6a809b1 in QAction::triggered (this=0x9c7e1d0, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#13 0xb6a81f32 in QAction::activate (this=0x9c7e1d0, event=QAction::Trigger) at kernel/qaction.cpp:1160
#14 0xb6ecf9cc in QMenuPrivate::activateCausedStack (this=0xac29228, causedStack=..., action=0x9c7e1d0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:967
#15 0xb6ed603b in QMenuPrivate::activateAction (this=0xac29228, action=0x9c7e1d0, action_e=QAction::Trigger, self=<value optimized out>) at widgets/qmenu.cpp:1060
#16 0xb6ed6bf7 in QMenu::mouseReleaseEvent (this=0xb01ae58, e=0xbfcfc820) at widgets/qmenu.cpp:2254
#17 0xb75c11c5 in KMenu::mouseReleaseEvent (this=0xb01ae58, e=0xbfcfc820) at ../../kdeui/widgets/kmenu.cpp:456
#18 0xb6adc012 in QWidget::event (this=0xb01ae58, event=0xbfcfc820) at kernel/qwidget.cpp:7549
#19 0xb6ed8e34 in QMenu::event (this=0xb01ae58, e=0xbfcfc820) at widgets/qmenu.cpp:2353
#20 0xb6a86f54 in QApplicationPrivate::notify_helper (this=0x9620750, receiver=0xb01ae58, e=0xbfcfc820) at kernel/qapplication.cpp:4056
#21 0xb6a8f033 in QApplication::notify (this=0xbfcfe204, receiver=0xb01ae58, e=0xbfcfc820) at kernel/qapplication.cpp:3758
#22 0xb74d6bfa in KApplication::notify (this=0xbfcfe204, receiver=0xb01ae58, event=0xbfcfc820) at ../../kdeui/kernel/kapplication.cpp:302
#23 0xb662a6cb in QCoreApplication::notifyInternal (this=0xbfcfe204, receiver=0xb01ae58, event=0xbfcfc820) at kernel/qcoreapplication.cpp:610
#24 0xb6a8df6e in QCoreApplication::sendSpontaneousEvent (receiver=0xb01ae58, event=0xbfcfc820, alienWidget=0x0, nativeWidget=0xb01ae58, buttonDown=0xb7301aa0, lastMouseReceiver=...)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#25 QApplicationPrivate::sendMouseEvent (receiver=0xb01ae58, event=0xbfcfc820, alienWidget=0x0, nativeWidget=0xb01ae58, buttonDown=0xb7301aa0, lastMouseReceiver=...) at kernel/qapplication.cpp:2924
#26 0xb6afcc87 in QETWidget::translateMouseEvent (this=0xb01ae58, event=0xbfcfde6c) at kernel/qapplication_x11.cpp:4343
#27 0xb6afbc4b in QApplication::x11ProcessEvent (this=0xbfcfe204, event=0xbfcfde6c) at kernel/qapplication_x11.cpp:3428
#28 0xb6b28502 in x11EventSourceDispatch (s=0x9618b68, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#29 0xb491ee78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0xb4922720 in ?? () from /lib/libglib-2.0.so.0
#31 0xb4922853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0xb665502c in QEventDispatcherGlib::processEvents (this=0x95f79f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#33 0xb6b27be5 in QGuiEventDispatcherGlib::processEvents (this=0x95f79f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0xb6628c79 in QEventLoop::processEvents (this=0xbfcfe164, flags=) at kernel/qeventloop.cpp:149
#35 0xb66290ca in QEventLoop::exec (this=0xbfcfe164, flags=...) at kernel/qeventloop.cpp:201
#36 0xb662b53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0xb6a86dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804b4e6 in main (argc=1, argv=0xbfcfe424) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-11 13:16:23 UTC 
- Have you tried to repeat the situation to check if the application crashes again ?
Thanks
Comment 2 pp.f. 2009-12-14 09:40:27 UTC 
On Friday 11 December 2009 13:16:24 Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=218141

> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  
2009-12-11
>  13:16:23 --- - Have you tried to repeat the situation to check if the
>  application crashes again ?
> Thanks
> 

Kmail doesn't crash now for Collapse all thread! Sorry for impatience. (it not 
work as expected, as it not collapse "all" threads, somewhat randomly, but 
this is not much an issue)

thank you
Comment 3 Myriam Schweingruber 2012-08-19 11:00:38 UTC 
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding