Bug 342932 - crash on exit of Sublime::IdealDockWidget::contextMenuRequested
Summary: crash on exit of Sublime::IdealDockWidget::contextMenuRequested
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: sublime (show other bugs)
Version: 1.7.0
Platform: MacPorts macOS
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-16 20:22 UTC by RJVB
Modified: 2018-12-01 03:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace showing the crash site (171.12 KB, text/plain)
2015-01-16 20:22 UTC, RJVB
Details
the patch mentioned in the report (3.23 KB, patch)
2015-08-31 11:52 UTC, RJVB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2015-01-16 20:22:24 UTC
Please see summary and the attached backtrace.


 

Reproducible: Didn't try

Steps to Reproduce:
1. Open a (large) CMake-based project
2. While it's parsing, rightclick somewhere in the frame to get the context menu that allows to "Locate current file"
3. Select that action

Actual Results:  
Crash.

Expected Results:  
Location of the current document - in the project tree I presume.

The crash occurs in the QMenu dtor after the KMenu dtor is called when the function exits. I'm currently testing a patch where `KMenu menu` is replaced with `KMenu *menu = new KMenu()` and the instance is deleted with menu->deleteLater().
Comment 1 RJVB 2015-01-16 20:22:58 UTC
Created attachment 90460 [details]
backtrace showing the crash site
Comment 2 Kevin Funk 2015-08-25 07:31:44 UTC
What about the patch?
Comment 3 RJVB 2015-08-25 08:21:19 UTC
Oops, I suppose that's the risk when you mention testing a patch without uploading it: you forget about it if it does its job, until you rebuild from a clean check-out or someone comes yanking your chair.
I'm going to have to go back in and see if I can unravel this!
Comment 4 RJVB 2015-08-31 11:52:22 UTC
Created attachment 94299 [details]
the patch mentioned in the report

Should I file a review request for this one?
Comment 5 Aleix Pol 2016-09-06 18:56:54 UTC
Yes please, and remember to fix the indentation first.
Comment 6 Andrew Crouthamel 2018-11-01 13:41:16 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 7 Bug Janitor Service 2018-11-16 11:33:50 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 8 Bug Janitor Service 2018-12-01 03:48:19 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!