I'm not sure why this happens, but it seems to happen with both
m4eclipse and q4e, or possibly its just an eclipse project generated
with eclipse:eclipse, but either way, My system grinds to a halt when
I compile from the command line with Eclipse running.
Specifically, I'll do: "mvn compile", while the same project is open
in Eclipse. There are 3255 source files to compile. The system grinds
to a halt, Eclipse 9and every other app) becomes unresponsive, and
system/root user CPU usage spikes to 100%, while 'user' CPU usage
plummets to nearly 0%. If I'm lucky, the process completes and I get
my computer back. If I'm unlucky, eclipse crashes.
What I think is happening is that Eclipse is monitoring changed files
somehow using a kernel hook, which is causing 100% CPU usage by the
system, which is preventing compiling from getting done. Or something
like that.
Anyone else seen this?
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
