Bug #125656 was reported against Eclipse 3.1 and was only fixed
recently - the fix should be in 3.2M6 that's due on 3/31. The bug
would freeze up keyboard input, the caret would stop flashing, but
you could sometimes shut Eclipse down with the mouse. I say
sometimes since I use multiple windows on multiple monitors and it
sometimes the bug would peg the CPU and lock up Eclipse completely.
Maybe that's the bug you saw?
On Mar 28, 2006, at 6:29 PM, Michael McDougall wrote:
How is Eclipse working for folks with DP7? For me, it has been
very solid, especially since we found and fixed "( 4400332 ) Crash
navigating in Eclipse" back in DP6. (Thanks Scott E, the crashlogs
were key)
However, I know I certainly don't put Eclipse under as much stress
as much as some of you folks out in java-dev land do.
One thing that has me concerned: several weeks back, I ran into a
problem where twice in two days, I did _something_ that triggered a
bug where Eclipse 3.1.2 permanently lost keyboard events in the
edit window; all typing was ignored. There wasn't a problem with
data-loss. All my menus still worked with the mouse, so I was
easily able to save and restart.
Since the time I saw these problems, I've bumped up to Eclipse
3.2M5, and we have rolled several developer previews. I've not
been able to reproduce the problem. Has anyone else got any
helpful clues? It's important to me that developers have solid
tools with which to work.
Michael McDougall
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/java-dev/sean_montgomery%
40baseview.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
