https://bugs.kde.org/show_bug.cgi?id=375968
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=375968
--- Comment #6 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=375968
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=375968
Alexander Potashev changed:
What|Removed |Added
CC||aspotas...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=375968
--- Comment #3 from Milian Wolff ---
I think this only can arise when we have a cycle in the import structure, i.e.
X -> Y -> X
and probably that is only triggered by python which is why I haven't seen that
ever. The importsCache afaik also guards aga
https://bugs.kde.org/show_bug.cgi?id=375968
--- Comment #4 from Milian Wolff ---
Yep, looking at the indices this becomes clear:
thread 11:
1474 -> 1473
thread 9:
1488 -> 1473
thread 8:
1585 -> 1473 -> 1474
thread 11 and thread 8 trigger the deadlock
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=375968
Milian Wolff changed:
What|Removed |Added
Product|kdevelop|kdevplatform
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=375968
Milian Wolff changed:
What|Removed |Added
Priority|NOR |VHI
--
You are receiving this mail because:
You
