[kdevelop] [Bug 358787] deadlock between background parser and code completion

2022-12-16 Thread Mahima Mantri
https://bugs.kde.org/show_bug.cgi?id=358787 Mahima Mantri changed: What|Removed |Added CC||man...@jamesknows.com --- Comment #10 from

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2022-05-03 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=358787 --- Comment #9 from Igor Kushnir --- Git commit a947074f0872ad3245b8c73679143998a88e3753 by Igor Kushnir, on behalf of Jonathan L. Verner. Committed on 01/05/2022 at 12:56. Pushed by igorkushnir into branch 'release/22.04'. Fix a crash in the "update

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2021-10-29 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=358787 --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/277 -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2019-06-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=358787 ms...@fastmail.com changed: What|Removed |Added CC||kf...@kde.org -- You are receiving this

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2019-06-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=358787 --- Comment #7 from ms...@fastmail.com --- Alright, now I believe I have actually figured this out for the deadlock I was seeing although I am not sure it is the same one reported in this ticket. I think Milian's suspicion of clang taking an exorbitant

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2019-06-21 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=358787 --- Comment #6 from ms...@fastmail.com --- Hmm, on second thought, it seems that the DUChain read lock is unlocked before createCompletionContext is invoked. Perhaps my above analysis is not the case. -- You are receiving this mail because: You are

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2019-06-21 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=358787 ms...@fastmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2019-06-21 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=358787 ms...@fastmail.com changed: What|Removed |Added CC||ms...@fastmail.com --- Comment #4 from

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2018-10-26 Thread Andrew Crouthamel
https://bugs.kde.org/show_bug.cgi?id=358787 Andrew Crouthamel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2018-09-25 Thread Andrew Crouthamel
https://bugs.kde.org/show_bug.cgi?id=358787 Andrew Crouthamel changed: What|Removed |Added Keywords||triaged --- Comment #2 from Andrew

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2016-02-21 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358787 Milian Wolff changed: What|Removed |Added Resolution|--- |WAITINGFORINFO

[kdevelop] [Bug 358787] deadlock between background parser and code completion

2016-01-30 Thread Milian Wolff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358787 Milian Wolff changed: What|Removed |Added Target Milestone|--- |5.0.0 Ever confirmed|0