You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Main thread (which is invoking hover) is waiting on a lock because it walks the project resources (due to executing the Sdf3GetSourceFiles task), and this lock is probably locked because the Spoofax LWB builder thread holds a lock on the entire project.
Spoofax LWB builder thread probably locks the entire project, but is stuck waiting on a lock for writing to the console.
It is unclear to me why the builder thread is stuck waiting on the console.
The text was updated successfully, but these errors were encountered:
Gohla
added
C-Bug
Category: bug. Not working as expected
P-High
Priority: high. Should take priority over low and non-prioritized
labels
Sep 17, 2021
Summary
A deadlock can occur sometimes when invoking hover/reference resolution in the Eclipse LWB.
What you did
Build a language and then invoke hover/reference resolution.
What you expected to happen
No deadlock to occur.
What actually happened
A deadlock occurs.
Context
Additional information
Thread dump: https://gist.github.com/Gohla/661524b25904b5010f3ddd98525a2057
The dump indicates that both the:
Sdf3GetSourceFiles
task), and this lock is probably locked because the Spoofax LWB builder thread holds a lock on the entire project.It is unclear to me why the builder thread is stuck waiting on the console.
The text was updated successfully, but these errors were encountered: