Bug 290118

Summary: Changing Settings->Sidebar causes KCachegrind to crash
Product: [Developer tools] kcachegrind Reporter: Kamal <matha>
Component: generalAssignee: Josef Weidendorfer <josef.weidendorfer>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version First Reported In: 0.5.1kde   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Kamal 2011-12-29 20:40:29 UTC 
Application: kcachegrind (0.5.1kde)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-37-generic i686
Distribution: Ubuntu 10.04.3 LTS

-- Information about the crash:
Start in a layout with Function Profile turned off. Check Settings->Sidebar->Function Profile.

 -- Backtrace:
Application: KCachegrind (kcachegrind), signal: Segmentation fault
[KCrash Handler]
#5  0x080da259 in CostListItem::updateName (this=0xbe58420) at ../../../kcachegrind/libviews/costlistitem.cpp:70
#6  0x080adf4f in FunctionSelection::updateGroupSizes (this=0x966c090, hideEmpty=false) at ../../../kcachegrind/libviews/functionselection.cpp:789
#7  0x080b07d6 in FunctionSelection::query (this=0x966c090, query=) at ../../../kcachegrind/libviews/functionselection.cpp:804
#8  0x080b1043 in FunctionSelection::doUpdate (this=0x966c090, changeType=85) at ../../../kcachegrind/libviews/functionselection.cpp:446
#9  0x080be8b0 in TraceItemView::triggerUpdate (this=0x966c0a4, force=false) at ../../../kcachegrind/libviews/traceitemview.cpp:309
#10 0x080be97c in TraceItemViewUpdateTimer::timeoutTriggered (this=0x96681b8) at ../../../kcachegrind/libviews/traceitemview.cpp:43
#11 0x080be9c3 in TraceItemViewUpdateTimer::qt_metacall (this=0x96681b8, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfa1de2c) at ./traceitemview.moc:72
#12 0x04e7ec9a in QMetaObject::metacall (object=0x96681b8, cl=135365856, idx=10, argv=0xbfa1de2c) at kernel/qmetaobject.cpp:237
#13 0x04e8d3d5 in QMetaObject::activate (sender=0x96681b8, m=0x811838c, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#14 0x04edeaa7 in QTimer::timeout (this=0x96681b8) at .moc/release-shared/moc_qtimer.cpp:134
#15 0x04e9560e in QTimer::timerEvent (this=0x96681b8, e=0xbfa1e360) at kernel/qtimer.cpp:271
#16 0x04e8a254 in QObject::event (this=0x96681b8, e=0x0) at kernel/qobject.cpp:1212
#17 0x010f64dc in QApplicationPrivate::notify_helper (this=0x93f5ff0, receiver=0x96681b8, e=0xbfa1e360) at kernel/qapplication.cpp:4300
#18 0x010fd05e in QApplication::notify (this=0xbfa1e6c8, receiver=0x96681b8, e=0xbfa1e360) at kernel/qapplication.cpp:3704
#19 0x00de940a in KApplication::notify (this=0xbfa1e6c8, receiver=0x96681b8, event=0xbfa1e360) at ../../kdeui/kernel/kapplication.cpp:302
#20 0x04e79a3b in QCoreApplication::notifyInternal (this=0xbfa1e6c8, receiver=0x96681b8, event=0xbfa1e360) at kernel/qcoreapplication.cpp:704
#21 0x04ea8d66 in QCoreApplication::sendEvent (this=0x93f8db4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 QTimerInfoList::activateTimers (this=0x93f8db4) at kernel/qeventdispatcher_unix.cpp:603
#23 0x04ea58e4 in timerSourceDispatch (source=0x93f8d80) at kernel/qeventdispatcher_glib.cpp:184
#24 0x01a785e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x01a7c2d8 in ?? () from /lib/libglib-2.0.so.0
#26 0x01a7c4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x04ea55d5 in QEventDispatcherGlib::processEvents (this=0x93e19c0, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#28 0x011b6135 in QGuiEventDispatcherGlib::processEvents (this=0x93e19c0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x04e78059 in QEventLoop::processEvents (this=0xbfa1e624, flags=) at kernel/qeventloop.cpp:149
#30 0x04e784aa in QEventLoop::exec (this=0xbfa1e624, flags=...) at kernel/qeventloop.cpp:201
#31 0x04e7c69f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0x010f6577 in QApplication::exec () at kernel/qapplication.cpp:3579
#33 0x080626ab in main (argc=2, argv=0xbfa1e814) at ../../../kcachegrind/kcachegrind/main.cpp:91

Reported using DrKonqi
Comment 1 Josef Weidendorfer 2012-01-09 16:39:18 UTC 
I tried to reproduce the problem with the current version
(0.7kde on KDE 4.7.3), but I was not able to.

As your version is already quite old: can you try it with
a newer one? I suppose this bug is an old issue with the
port from Qt3-compatibility classes in Qt4 to real Qt4
classes.
Comment 2 Kamal 2012-01-09 16:49:26 UTC 
OK. I will give it a try when I am back in that space (moved on to something else for the moment). 

Cheers,
Kamal

-----Original Message-----
From: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] On Behalf Of Josef Weidendorfer
Sent: Monday, January 09, 2012 11:39 AM
To: Kamal Ahmed
Subject: [Bug 290118] Changing Settings->Sidebar causes KCachegrind to crash

https://bugs.kde.org/show_bug.cgi?id=290118





--- Comment #1 from Josef Weidendorfer <josef weidendorfer gmx de>  2012-01-09 16:39:18 ---
I tried to reproduce the problem with the current version
(0.7kde on KDE 4.7.3), but I was not able to.

As your version is already quite old: can you try it with
a newer one? I suppose this bug is an old issue with the
port from Qt3-compatibility classes in Qt4 to real Qt4
classes.
Comment 3 Josef Weidendorfer 2013-04-05 15:32:27 UTC 
Any chance to reproduce this with a current version?
Comment 4 Andrew Crouthamel 2018-10-30 00:00:28 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-14 11:28:37 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2018-11-29 09:36:36 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!