[jbosstools-dev] Be aware of nasty Indigo File leak!
Max Rydahl Andersen
max.andersen at redhat.com
Tue Jun 14 02:55:22 EDT 2011
Hi,
This is about https://bugs.eclipse.org/bugs/show_bug.cgi?id=349105
Over the last couple of weeks we have had several bugs being reported on Linux systems in many parts of the
tooling about running out of file descriptors for no apparent reason.
Yesterday Snjezana discovered that the possible root cause for many of these are that equinox (the base of osgi in eclipse)
were not closing of the inputstreams of all jars in your eclipse install when you run with -clean OR after a fresh install/update
from an updatesite.
This causes Eclipse to crash almost instantly OR if you have a "smallish" installation it will survive for a while but then crash
when some operation in eclipse requires a bunch of file descriptors and crosses the magical "1000" limit Linux installations
by default run with.
The bug turned out to be a regression in Eclipse 3.7 codebase, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=349105 for
details and is currently in review for inclusion in the final release.
This mail is to just let you be aware of that if you get issues about file descriptors running out then restart eclipse and retry.
If it still fails then the problem is most likely still in your code, if it does not fail it is most likely caused by this Indigo regression.
FYI, on linux and mac you can see what files are held open by Eclipse by using lsof -p <pidofeclipse>
2XFYI, Mac users aren't affected by this since ulimit is set to unlimited and Windows does not have this kind of limitation. GAM or GAP! :)
/max
http://about.me/maxandersen
More information about the jbosstools-dev
mailing list