https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #31 from David Nolden ---
Could you check whether the python plugin (both of its components) are
loaded/unloaded before the crash happens? (you could do it with the patch I
attached)
For me, the python language supports are always unloaded
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #30 from David Nolden ---
Created attachment 114532
--> https://bugs.kde.org/attachment.cgi?id=114532&action=edit
Patch to debug loading/unloading of python plugin
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #27 from David Nolden ---
Created attachment 114420
--> https://bugs.kde.org/attachment.cgi?id=114420&action=edit
Hack setting all language-support plugins to AlwaysOn
Can you try if this hack works for you? (I'm testing it
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #26 from David Nolden ---
These are not "language IDs", but rather "item IDs", and the mapping from
identity to a factory (and thus to a language plugin) only exists when the
plugin is loaded. Otherwise these ar
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #24 from David Nolden ---
I've checked the identities, and all the duchain item identities that you
mentioned before belong to the kdev-python plugin, so my guess is now that the
kdev-python plugin was unloaded.
I've further tho
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #22 from David Nolden ---
The reason why it helps is probably because it simply avoids the recursive
destruction and data reclaim mechanisms. And if the data ranges are not put
into the "free list", they will never be touched agai
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #21 from David Nolden ---
I'm not saying what you're doing is bad, but it's probably not the most
sustainable way to fix it. For example, this may leave unclaimed data in the
duchain disk cache which will also consume memor
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #20 from David Nolden ---
Doing cleanup much earlier, e.g. in aboutToQuit, would probably be difficult,
because you need to make sure that no duchain data structures (e.g.
IndexedString) are accessed after that. All parsing must be finished
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #18 from David Nolden ---
Btw. the cleanup is mainly concerning the on-disk cache structure.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #17 from David Nolden ---
It doesn't make sense to fiddle around with the internals of the hash, when
this only happens during shutdown.
The question is what's different during shutdown than during the earlier
cleanup calls.
https://bugs.kde.org/show_bug.cgi?id=364971
--- Comment #4 from David Nolden ---
The patch was actually quite trivial, the conditional "if
(static_cast(problem->m_diagnostics.size()) !=
problem->d_func()->diagnosticsSize())" simply needed to be removed so that
indices are up
https://bugs.kde.org/show_bug.cgi?id=364971
David Nolden changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/kdev
https://bugs.kde.org/show_bug.cgi?id=350409
David Nolden changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=364971
--- Comment #1 from David Nolden ---
Note that I'm currently testing a patch to fix this. Until now it seems to
work. I'll commit it if the bug doesn't reappear. The trick is to always
re-index the child diagnostics in
Loca
https://bugs.kde.org/show_bug.cgi?id=364971
Bug ID: 364971
Summary: Frequent Crash in ProblemStore::addDiagnostic due to
endless recursion
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=358853
David Nolden changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
https://bugs.kde.org/show_bug.cgi?id=358853
David Nolden changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=358853
--- Comment #5 from David Nolden ---
Git commit c9dcbaeedef2ec746214d1be91a09293492e4abb by David Nolden.
Committed on 01/02/2016 at 18:15.
Pushed by zwabel into branch '5.0'.
Add a testcase for BUG: 358853
It seems to break as soon as
https://bugs.kde.org/show_bug.cgi?id=358853
--- Comment #5 from David Nolden ---
Git commit c9dcbaeedef2ec746214d1be91a09293492e4abb by David Nolden.
Committed on 01/02/2016 at 18:15.
Pushed by zwabel into branch '5.0'.
Add a testcase for BUG: 358853
It seems to break as soon as
https://bugs.kde.org/show_bug.cgi?id=358853
--- Comment #4 from David Nolden ---
Git commit a1d6a13183c01b9ea2c45e470e81f9ec53df7ada by David Nolden.
Committed on 01/02/2016 at 18:11.
Pushed by zwabel into branch 'master'.
Always show recursive "missing include" errors in
https://bugs.kde.org/show_bug.cgi?id=358853
--- Comment #2 from David Nolden ---
Git commit 7bdc9e8d9539c6e904edbd021d0cc359cdc8e843 by David Nolden.
Committed on 01/02/2016 at 15:53.
Pushed by zwabel into branch 'master'.
Add a testcase for BUG: 358853
It seems to break as soon as
https://bugs.kde.org/show_bug.cgi?id=358853
Bug ID: 358853
Summary: include not found in a header causes random
parsing/highlighting/code completion glitches
Product: kdevelop
Version: git master
Platform: unspecified
22 matches
Mail list logo
