Community
Participate
Working Groups
M4 candidate being tested Steps, maybe not reproducable: - start brand new eclipse - File -> New -> Project... - select Plug-in Development - Plug-in Project, Next - set name to "asd" (no quotes), Next - Next - select Hello World, Next - Next - Finish - answer Yes to "switch to Java perspective" dialog if it comes up - the cigarette will appear, I'm guessing to indicate the code generation is being done - after a few seconds it freezes, and the desktop has died - will attach the dump that kill -3 gave next
Created attachment 6396 [details] trace
*** Bug 44595 has been marked as a duplicate of this bug. ***
*** Bug 44599 has been marked as a duplicate of this bug. ***
*** Bug 44603 has been marked as a duplicate of this bug. ***
I'm lumping these deadlocks together, even though they have nothing in common in the stack trace and different steps to reproduce. This VM is deadlocking every few minutes, so I suspect a VM bug. Here are the symptoms I observe in this particular hang: - CPU remains pegged at 98% - Successive stack dumps over a ten minute period show *all* threads in exactly the same state. Animate loop is running in one job, autobuild is running in another. Main thread is waiting on autobuild. Autobuild and animate loops are not blocked on any lock or monitor, but they are in the same stack across thread dumps. Other interesting notes: - this is the first time running on this particular 1.4 VM - Other flavours of Motif on other *nixes are not deadlocking
Using the new 1.4.1 vm I couldn't get Eclipse 2.1.1 to freeze, but I did get Eclipse 3.0M2 and Eclipse 3.0M3 to freeze, and this didn't happen before when we were still using the 1.3 vm. So it's likely a vm problem, which means that eclipse is approaching unusable on aix since a 1.4.1 vm is now required.
When the JIT is turned off (-Djava.compiler=NONE), the freezing does not seem to occur. Summary of situation: the IBM 1.4.1 build (20030522) we have available for AIX is unusable for Eclipse 3.0 stream builds with JIT turned on. With JIT turned off, it is usable (but extremely slow). The last IBM 1.3 VM we had was working fine up until about two weeks ago, after which components began to add code that required a 1.4 VM. Eclipse 2.1.1 still works with the 1.4 VM. Since we have introduced much more concurrency in 3.0 stream, I suspect that this is a JIT bug relating to threading and/or java monitor synchronization.
This looks like an issue that needs to be raised with the VM vendor.
Changing comment to reflect general nature of the problem. The VM just starts hanging after a few minutes of use when JIT is turned on.
Closing - this was a VM problem.
