https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #51 from RJVB ---
I too only seem to be getting this crash only sporadically nowadays, and AFAICT
there's (almost) always a prematurely unloaded language plugin involved. But
I'm pretty certain it does not only occur after working with a
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #50 from Igor Kushnir ---
I rarely experience freeze on exit and even more rarely this particular freeze
(lately, once a year perhaps despite heavy KDevelop use). Yesterday I got the
currentIndex=0 freeze. Note the `followerIndex (index=0,`
https://bugs.kde.org/show_bug.cgi?id=379669
Igor Kushnir changed:
What|Removed |Added
CC||joerg.stre...@gmail.com
--- Comment #49 from
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #48 from Aaron Williams ---
I am still seeing this in the latest release.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #47 from RJVB ---
> The problem is that currentIndex is 0 and it never bails out. This is with
> the very latest release.
IIRC this is one of the things my patch addresses.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #46 from Aaron Williams ---
I too am getting the hangs on exit. In the debugger I see it failing in
KDevelop::Bucket::deleteItem > (repository=...,
hash=, index=29676, this=0x55850f6084f0) at
https://bugs.kde.org/show_bug.cgi?id=379669
Igor Kushnir changed:
What|Removed |Added
CC||aar...@doofus.org
--- Comment #45 from Igor
https://bugs.kde.org/show_bug.cgi?id=379669
Lemuel Simon changed:
What|Removed |Added
CC||lemuelsimo...@protonmail.co
|
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #43 from RJVB ---
I also am continuing to get hangs on exit, but a while back I implemented a
failsafe, a simple timer that raises a SIGHUP if the application doesn't exit
normally within 1 minute after starting the final cleanup. Nowadays
https://bugs.kde.org/show_bug.cgi?id=379669
Igor Kushnir changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=379669
Raúl changed:
What|Removed |Added
Version|5.6.1 |5.6.2
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #42 from Raúl ---
Hello:
Still happening on 5.6.2. Debian testing, KDE Frameworks 5.78.0, Qt 5.15.2
Thread 23 (Thread 0x7f8b60f90700 (LWP 3684) "KDevelop::Compl"):
#0 0x7f8bf8da73ff in __GI___poll (fds=0x7f8b3809e7a0, nfds=1,
https://bugs.kde.org/show_bug.cgi?id=379669
Igor Kushnir changed:
What|Removed |Added
CC||igor...@gmail.com
Version|5.5.0
https://bugs.kde.org/show_bug.cgi?id=379669
Piotr Keplicz changed:
What|Removed |Added
Version|5.4.6 |5.5.0
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=379669
Piotr Keplicz changed:
What|Removed |Added
CC||kepl...@cmc.pl
--- Comment #41 from Piotr
https://bugs.kde.org/show_bug.cgi?id=379669
Raúl changed:
What|Removed |Added
Version|unspecified |5.4.6
--- Comment #40 from Raúl ---
Hi!
This is just
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #39 from RJVB ---
Just wondering, when in my patch I bail out from an otherwise endless loop and
thus leave at least 1 entry undeleted, do those get deleted at runtime in a
future session? Or do they risk ending up hanging around because
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #38 from Thomas Schöps ---
Yes, I could imagine that there are such problems and the procedure that you
describe might be better. But I am not knowledgeable enough about the KDevelop
architecture to make any well-informed decisions here.
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #37 from RJVB ---
Couldn't there be a chicken-and-egg situation here? I wouldn't be surprised if
certain plugins need DUchain to be present & working, and wouldn't a reliable
shutdown procedure look something like the following?
- tell
https://bugs.kde.org/show_bug.cgi?id=379669
Thomas Schöps changed:
What|Removed |Added
CC||tom.scho...@gmail.com
--- Comment #36 from
https://bugs.kde.org/show_bug.cgi?id=379669
Aleksey Midenkov changed:
What|Removed |Added
CC||midenok+kdeb...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=379669
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #35 from RJVB ---
Created attachment 121377
--> https://bugs.kde.org/attachment.cgi?id=121377=edit
June 2019 version of the workaround patch
I've been maintaining the patch and adding the occasional tweak to it to catch
newly identified
https://bugs.kde.org/show_bug.cgi?id=379669
RJVB changed:
What|Removed |Added
Attachment #113627|latest version of the |June 2018 version of the
description|workaround
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #34 from RJVB ---
Created attachment 116580
--> https://bugs.kde.org/attachment.cgi?id=116580=edit
terminal log
Here's a log showing an exceptionally large number of caught issues where a
hang would have resulted during the global
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #33 from RJVB ---
FWIW, I haven't seen hangs in a while with my workaround patch applied. Debug
output showing that hang situations were handled appears quite regularly
though.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=379669
Kevin Funk changed:
What|Removed |Added
CC||ricardo@hotmail.com
--- Comment #32 from
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=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 #29 from RJVB ---
Created attachment 114422
--> https://bugs.kde.org/attachment.cgi?id=114422=edit
example on-exit terminal output with the "AlwaysEnable" patch
I saw that setting AlwaysEnabled also makes a plugin "ununloadable" ... but
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #28 from RJVB ---
No guarantees I'll get around to that the next 2 weeks (and even less so that
I'd get the issue during that time!)
BTW, how is this supposed to help if the issue is caused by unloading plugins
too early? Doesn't that mean
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=edit
Hack setting all language-support plugins to AlwaysOn
Can you try if this hack works for you? (I'm testing it now, but I'm not
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 are just unknown items.
--
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 thought about
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #23 from RJVB ---
> Maybe your other crashes with "project unloading" were also related to
> unloaded language plugins. Which language plugins do you use?
Possibly, but I cannot remember if I had any "interesting" terminal output at
the
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 again and also
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 memory in succeeding
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
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #19 from RJVB ---
>From memory, my patch mostly introduces common-sense error handling, it doesn't
change anything else in the hash internals. I don't understand those, so I keep
my hands off. I don't even understand why my attempts at
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.
The last
https://bugs.kde.org/show_bug.cgi?id=379669
Raúl changed:
What|Removed |Added
CC||rasas...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=379669
RJVB changed:
What|Removed |Added
Attachment #105591|0 |1
is obsolete||
---
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #15 from RJVB ---
I now have a session that will print a huge list of debug messages
systematically at exit, from one of the places where I added anti-hang
protections. Always about types 62 and 63, plus a few type 59 and 64 at the
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #14 from RJVB ---
I just had another of these fits, in the 5.2 branch (and not running that patch
of mine AFAIK):
* thread #1: tid = 0x1a89e11, 0x00010a28f93a
libKDevPlatformLanguage.10.dylib`void
https://bugs.kde.org/show_bug.cgi?id=379669
Kevin Funk changed:
What|Removed |Added
CC||david.nolden.kde@art-master
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #12 from Francis Herne ---
I just got this hang with 0f101e4c1 (master as of three days ago), so I'm
afraid this doesn't seem fixed yet in all cases.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #11 from Kevin Funk ---
Git commit 6fb0143838087cc430d95dc406e3f7e684d9d6b9 by Kevin Funk.
Committed on 07/08/2017 at 07:50.
Pushed by kfunk into branch '5.1'.
backgroundparser: Ensure jobs are finished on exit
Summary:
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #10 from RJVB ---
FWIW, I haven't seen the hang since applying your patch (but I'm not sure we
can cry victory yet, the issue was always highly unpredictable).
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #9 from Kevin Funk ---
Git commit 0714e5d52abedbf73cebab5986905a3841b68449 by Kevin Funk.
Committed on 04/08/2017 at 08:46.
Pushed by kfunk into branch '5.1'.
TypeRegister: Stronger assumptions in debug mode
All of these
https://bugs.kde.org/show_bug.cgi?id=379669
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #8 from RJVB ---
FWIW, even when this hang doesn't occur KDevelop can take forever to shutdown.
The other day I had the source trees for GCC 6.3.0 and 7.1.0 open in respective
projects in a single session. I'm not
https://bugs.kde.org/show_bug.cgi?id=379669
Francis Herne changed:
What|Removed |Added
CC||m...@flherne.uk
--- Comment
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #6 from RJVB ---
Is there any chance this and #379977 could somehow be related? The "easy"
explanation would be if another thread (or 2) were locked in a never-ending
wait to get a duchain lock but I don't see any
https://bugs.kde.org/show_bug.cgi?id=379669
RJVB changed:
What|Removed |Added
Attachment #105432|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=379669
RJVB changed:
What|Removed |Added
Attachment #105430|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #3 from RJVB ---
Created attachment 105430
--> https://bugs.kde.org/attachment.cgi?id=105430=edit
my current test patch
Good to see this confirmed and bumped to a higher priority.
I've attached the patch I'm
https://bugs.kde.org/show_bug.cgi?id=379669
Kevin Funk changed:
What|Removed |Added
Ever confirmed|0 |1
Priority|NOR
https://bugs.kde.org/show_bug.cgi?id=379669
Kevin Funk changed:
What|Removed |Added
Summary|KDevelop continues to hang |KDevelop continues to hang
59 matches
Mail list logo