Summary: | spellchecker crashes kdevelop during shutdown | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Andreas Pakulat <apaku> |
Component: | kspell | Assignee: | Zack Rusin <zack> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | cfeck, justin.zobel, michel.ludwig |
Priority: | NOR | ||
Version First Reported In: | SVN | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Andreas Pakulat
2009-07-17 01:04:53 UTC
With revision 998207 of kdelibs/kdevplatform/kdevelop and with one open .cpp file, I cannot reproduce the crash. KDevelop doesn't terminate properly, though. I get a constant stream of kdevelop(29166)/kdevelop (cpp support) UIBlockTester::lockup: ui is blocking Still reproduceable here with kdelibs r998175. I also get a warning about 1 dictionary not being free'd during shutdown. I've had 2 projects opened and parsed by kdevelop and one file open from one of the projects. Ok, I've installed enchant and now I get the warning, but still no crash. Anyway, this looks like a Sonnet issue to me. Does it also crash for you in Kate/KWrite? No, kate doesn't crash. I'm wondering wether the problem is order of cleanup of global statics... KDevelop has a couple more than kate I'm guessing. Still very annoying, is there a way to disable the spellchecker, code-wise? As I won't be diving into the sonnet code, we might have to disable creation of the on-the-fly-spellchecker in kdevelop if nobody else can fix this. Once I disable the CPP language support, termination doesn't block anymore and I get the crash as well. I've just committed a fix which ensures that no Sonnet-related object is created as long as no spell checking is taking place. This should help until the real problem is fixed. I'll try and see what I can do about it. (In reply to comment #5) > Once I disable the CPP language support, termination doesn't block anymore and > I get the crash as well. Hmm, that shouldn't be needed of course... > I've just committed a fix which ensures that no Sonnet-related object is > created as long as no spell checking is taking place. This should help until > the real problem is fixed. I'll try and see what I can do about it. Thanks a lot, I'll re-assign this to sonnet then. In revision 1002673 I've now changed the way how Sonnet::Speller objects are handled. More specifically, they are destroyed whenever documents are deleted. It seems that this fixes the problems with KDevelop. *** Bug 200250 has been marked as a duplicate of this bug. *** Thank you for the report, Andreas. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Lets assume this has been fixed, it appears I did not retest the last fix 11 years ago but I wouldn't be able to retest this these days anymore anyway. |