Description of problem:
I'm using Java Sun 5 (1.5.012). Eclipse will hang sometimes while compiling,
while other times attempting to open .java or .jsp files.
I haven't been able to trace the error, but it hangs so often, I figure I could
help trace down the bug.
Version-Release number of selected component (if applicable):
Fedora Eclipse 3.2.2 with WTP
Very very often.
Steps to Reproduce:
1. Open Fedora Eclipse and configure Sun's JRE
2. Use Eclipse as normal
3. Open a JSP file.
Screen will hang. Waiting 30 mins will not solve the error.
I'm using WTP. Installed from within Eclipse from site:
Created attachment 157634 [details]
Log of errors
Unfortunately, we can't really support this situation because a) it's being run
with a non-free VM and b) you're using WTP which we don't package :( A brief
look at the log you attached shows that something's missing JEM which is
provided by the Visual Editor but I doubt that's your problem.
Perhaps you should try an upstream WTP download -- they provide "all in one"
downloads that include all of their dependencies -- and see if your hangs still
occur. At least then we could see if it's something in our SDK packages that's
causing this. I doubt it is, but it's not entirely impossible.
Can you provide some details on your machine? Also, what is in
/usr/share/eclipse/eclipse.ini? You may try messing with the memory limits in
there (the -Xmx lines). We don't munge them at all because gij doesn't use
them, but the Sun VM you're using will respect them.
Sorry it took so long to respond.
I installed Upstream "WTP- All in One", still hangs when loading JSPs, and
sometimes when doing heavy processing.
Its a lot less frequent though.
The only thing I had in eclipse.ini was -debug -clean, but I also tried leaving
it empty, and setting the Xmx and Xms lines to 512 and 256. The higher the
number, the more frequently it hanged.
I have 2 gigs of RAM, so I doubt the error is there.
Since you're using the upstream download and it still hangs, I'd suggest asking
on the WTP newsgroup(s) or filing a bug against them at bugs.eclipse.org.