https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #25 from RJVB <rjvber...@gmail.com> ---
I wouldn't be surprised if kdev-python were involved (if not only because I
don't update it very often, nor do I usually rebuild/reinstall after KDevelop
upgrades - I guess I'm not the only one in that position?).
FWIW (and this links to your point 2) I don't always have kdev-python loaded,
esp. not in session for the KDevelop sources, and that's the one where I get
the crash/hang most often.
FWIW2: Qt itself has stopped unloading most plugins on exit a few releases ago,
exactly because it's almost impossible to guarantee that no race-conditions
will occur (for generic plugins). But will not unloading language plugins
guarantee that none of the various situations my patch handles will occur?
Also, if this indeed happens only with unloaded language plugins, does each
repository item know which plugin it goes with? If so, wouldn't it be possible
and maybe preferable to maintain a table of loaded plugins that registers when
they've been unloaded, and then skip items that go with an unloaded plugin?
FWIW3: it'd be very useful if error messages printed the language instead of
the language ID
```
kdevplatform.language: Cannot load a top-context from store
"/home/bertin/.cache/kdevduchain/kdevelop-{f793a513-f14e-47b9-8448-06ca72900c04}/topcontexts/data.mdb:#3619"
- the required language-support for handling ID 110 is probably not loaded
```
--
You are receiving this mail because:
You are watching all bug changes.
