On 6/15/2012 5:08 PM, Genestro wrote:
> All the Java IDEs seem to suffer from a related problem: if one is left
> open and idle for a while, it freezes and gets reported by the OS as
> "not responding" for a significant time (usually several full minutes)
> if you then switch to it and try to start using it again.
> Eclipse and Netbeans, in particular, are both guilty of this behavior.
Strange. I've used NetBeans since the 3.x days (that is, since
before it was usable) and am now using 6.8 (I dislike 7.x), and have
never seen what you report, nor anything like it. I've also used
Eclipse some (although only on Linux, and not nearly as much), and
have not observed anything along those lines. I imagine there must
be something rather different in our environments, but I don't have
any idea what it could be.
The O.P.'s report sounds a bit different from yours, though: He
mentions delays when firing up Eclipse the first time after not using
it for "one or two weeks," and doesn't say anything about letting it
sit open but idle, or about switching tasks. The "one or two weeks"
aspect made me wonder about auto-update or auto-patch activities, or
maybe about auto-resync with a version management system that's been
absorbing a lot of changes while he was away (so maybe there's a lot
of metadata to catch up on). But I'm dubious about that hypothesis,
since it doesn't square well with his report of high CPU activity --
fetching a lot of updates or metadata might take half an hour over a
slow network, but shouldn't peg the CPU ...
"Is a puzzlement!"