Community
Participate
Working Groups
Quite often, eclipse stops being able to do any sort of Java-based search. The symptom is always the same: the dialogue box just sits there forever. If I choose "Details", then the status will be "Searching - N files to index" (N varies; at the moment it's 1, but I've also seen other small numbers like 4 and so on there). Once eclipse gets into this state, no Java-based search will ever work again; I have to do file-based searches instead (which always work). Closing and reopening the project in question does nothing -- in fact, I just tried that, and now it's saying "19 files to index" an still not completing. I generally have to close and re-open eclipse to get Java searches to work again. I can't tell what's going on when this happens, and nothing appears to go into the .metadata/.log file or anything. Is there something further I can do to help track this down, the next time it happens? Eclipse 3.1M4 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) Linux-GTK (based on Red Hat 9, but with many packages updated)
I see you're running eclipse using a Sun 1.5.0-b64 VM... Can you make a try with a Sun 1.4.2 VM and let us know if this problem still occurs? (FYI, Eclipse 3.1 targets: http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html#TargetOperatingEnvironments)
this happens to me as well when running under Windows with JDK 1.4.2_03 try the following workaround which works for me: in the Java Search tab of the Search dialog, define a Working Set includes the source code scope you'd like to search and use it instead of the default Workspace scope, do this by using the Working Set radio button
one more comment: I sometimes had an "Out Of Memory" errors following the searhing problem described above, I changed my -vmargs settings and it seems that the search is now working fine my settings are: -vmargs -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M -XX:MaxNewSize=32M - XX:NewSize=32M -Xmx256m -Xms256m
Seems to be a duplicate as changing VM args solve the problem *** This bug has been marked as a duplicate of 80118 ***
