| Summary: | KDevelop crash while idle | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Christopher Heiny <christopherheiny> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | crash | CC: | |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Christopher Heiny
2016-10-27 19:21:54 UTC
The crash is in the cleanup thread which cleans up the code database and stores items to disk periodically. Did you do something to the file system containing ~/.cache (unmount it, ...?) Other than that, it's possible that the database is corrupted from an earlier crash. Clearing it might help if the problem is reproducible; just delete ~/.cache/kdevduchain while kdevelop is not running. Or it might be an actual bug in the cleanup code, but without a way to reproduce it and/or debug symbols in the trace I don't think we'll find it. Hi Sven, Sorry for the delay in replying. Your suggestion in the first paragraph is accurate - an errant system administration script deleted /home out from under everyone (note to sysadmins: it's test *first*, deploy *second*). /home has been restored as of this morning - you got to the bug before I could follow up. It's OK with me if you close this, or leave it open as a "we should handle this gracefully" request. Thanks! Chris I think we can close this, if you delete our persistent database we crash -- I guess that holds true for a lot of programs. Thanks for the update! |