Community
Participate
Working Groups
Created attachment 75114 [details] Screen capture after error occurred, showing file in editor and package explorer. Build ID: I20070625-1500 Steps To Reproduce: 1.Trigger a build More information: This error sometimes occurs when a build is triggered. The file in question can be edited, saved, updated, committed, etc. Refreshing or cleaning does not get rid of the error. The only way to continue working is to restart eclipse and THEN refresh, but sooner or later the error recurs. Usually the error occurs with the same file, but not always. I have not experienced this problem using eclipse 3.2.* or earlier. The bug is not that the error occurs, which might have nothing to do with eclipse, but that it cannot be gotten rid off without restarting. Some kind of caching problem?
Anything in .log?
Created attachment 75198 [details] workspace/.metadata/.log
Moving to JDT Core. They might be able to give more information when/why that problem gets reported.
This error is written when a CoreException occurs while reading the content of a java file during the build. Did you attach the .log file just after having this message or did you perform some other actions before send it to us?
The later, after removing a bunch of ...OutOfMemoryError: PermGen space errors from the front of .log. I now see that even after adding -XX:MaxPermSize=128m to eclipse.ini, I am still getting "...OutOfMemoryError: PermGen space" errors during "Period workspace save." in the .log, although eclipse does not crash. I will try increasing to 256m.
Fwiw, after increasing MaxPermSize to 256m I am no longer getting the OutOfMemory errors, but I am still getting "A handler conflict occurred..." warnings and exceptions caused by "(Too many open files)" errors. File descriptors limit is set to 1024 on our systems. I cannot work in eclipse for more than a couple of hours, and several times I have lost work because open files could not be saved. I am on the verge of deciding that 3.3 is unusable and switching back to 3.2.2.
I've done some comparison of eclipse 3.2.2 vs 3.3.0, and it appears that 3.3.0 has about an order of magnitude more open files then 3.2.2....
(In reply to comment #7) > I've done some comparison of eclipse 3.2.2 vs 3.3.0, and it appears that 3.3.0 > has about an order of magnitude more open files then 3.2.2.... > How did you measure it? Note that you use other plugins on top of Eclipse SDK which may be responsible of this magnitude...
I am getting the same error message. * Ganymede 3.4.2 * Fedora 9: 2.6.25.10-86.fc9.i686 #1 SMP Mon Jul 7 20:46:03 EDT 2008 i686 i686 i386 GNU/Linux It seems to be random - sometimes it works fine, then all of a sudden a bunch of files cannot be read. Refreshing, full clean, partial clean - nothing helps. The files are there since I can open them in the editor. Most of the files that cannot be read haven't been modified in a long time, others were modified recently. Very annoying...
Do you still get this issue with 3.5? If yes, does this file have a specific encoding set ?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
