Bug 155313 - konqueror stops responding and may crash after kcachegrind has been launched. kdeinit error
Summary: konqueror stops responding and may crash after kcachegrind has been launched....
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2008-01-09 01:21 UTC by Tiago Freitas
Modified: 2018-10-21 04:45 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 Tiago Freitas 2008-01-09 01:21:16 UTC
Version:           4.00.00 (KDE 4.0.0) (using KDE 4.00.00 (KDE 4.0.0), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.20-15-generic

If you go to applications:/Development/ in Konqueror and launch kcachegrind, Konqueror stops responding, and I think it memory leaks.

If you close kcachegrind, this error is presented:

KDEInit could not launch '/storage/tmp/kde4dev/kde/bin/kcachegrind'.

And konkeror returns back to normal, unless it SisegV (it happened twice but I can't reproduce the steps).

If you wait enough the whole system can stop with a black screen (I launched xkill and got the black screen), a X restart solves it.

If you launch kcachegrind with Alt+F2 instead of Konqueror, the same error appears, but Konqueror remains working well if you leave kcachegrind opened, so I think there is a problem in both Konqueror, kdeinit and maybe kcachegrind.
Comment 1 Dario Andres 2009-01-26 16:02:05 UTC
Can you still reproduce this bug with a recent KDE (4.1.4 / 4.2beta2 / 4.2rc1 / 4.2.0 / 4.2svn / 4.3svn) ? Thanks :)
Comment 2 Dario Andres 2009-05-29 20:03:37 UTC
Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-19 04:34:18 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 4 Andrew Crouthamel 2018-10-21 04:45:56 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!