https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #3 from RJVB <rjvber...@gmail.com> --- Have you read the ticket and commit message? I cannot reproduce the issue at will either. It happens and *will* (always?) provoke a crash, but it does so seemingly randomly. If you want to run each and every KDevelop session under a debugger with a breakpoint set, be our guest (our as in everyone using the app). I don't have the resources for that. I don't agree with your analysis in this case. There's no point in setting up a DocumentationView when the application is exitting. Nothing done in that ctor is crucial unless you use the instance, and that's not going to happen. Alternatively, please provide a utility to print a backtrace in ICore or wherever appropriate if there isn't already. I'll use that to determine where the call comes from. (Yes, I could write such a utility class myself but this time I'm going to leave it to some of the powers that be who don't need drawn-out review procedures.) Oh, and you could have left the secondary fix in that commit. -- You are receiving this mail because: You are watching all bug changes.
