I'm running the Ganymede release of Eclipse/WST, and I'm getting
situations where -- and this is happening as I type this -- Eclipse is
simply sitting here using between 160-200% of the CPU to run a
"Validation Monitor" whose status in the progress monitor indicates that
it's blocked on something. I was going to copy the message, but in the
time it took for the UI to repaint when I moved this mail windows out of
the way (2 minutes, if you're counting) the progress operation had
cleared itself, and now I can't get the message back.
I have gotten to the point where step one of any project creation for me
is to disable all validation tools; they do this for each and every
project for which I've enabled them. I don't lack for processor
resources or RAM -- Eclipse is run with -Xmx2048m and I have a dual-core
2.66Ghz CPU -- but I cannot consistently get validation to work any
faster than "wait 10 minutes for any part of your machine to respond"
which seems... inconvenient. I haven't managed to find a consistent
trigger for this.
I'm certainly willing to try some test cases if anyone thinks it will
help. As it is, some days it'd be faster to edit my java code in emacs,
and that's just madness :)
--
Chris Rose
Developer Planet Consulting Group
(780) 577-8433
crose@xxxxxxxxxxxx