-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FileInfoReader deadlock #568
Comments
This code looks a bit suspicious on the other hand its there since 16 years now, so there are likely better ways today to solve this. One part is also this one Line 150 in 65348d6
it only notifies one thread, not all threads waiting... beside that it seem to be blocked in |
The value of the barrier (true/false) was never read. It was only checked for !=null. The value had been read in waitOnSelf() without any multithreading semantics like synchronize/volatile. Instead now we use a thread safe AtomicBoolean. The synchronization blocks are still used for wait()/notifyAll() eclipse-equinox#568
Thread State / Dump would be more interesting than CPU sampling. e.g. why does PDE hinders the IDE to start at all? |
|
From that stacktrace it seem to hang in a Java Editor that triggers init of classpath while showing a view (what triggers PDE to do something). Still I'm wondering why all this happens before the UI is displayed.... |
waitOnSelf() does not synchronize the read on that while org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader.handleRemoteFileEvent(IRemoteFileSystemEvent) does synchronize for write
Originally posted by @jukzi in eclipse-pde/eclipse.pde#1481 (comment)
original reports:
eclipse-pde/eclipse.pde#1481
eclipse-pde/eclipse.pde#1160
The text was updated successfully, but these errors were encountered: