I've just started using Netbeans 3.6 (on Win XP). It quite often freezes when I'm happily typing away and, particularly, if I switch to another window, e.g. IE or Outlook and then back again. These freeze periods can be up to a couple of minutes at a time.
I used Netbeans about 18 months ago and had similar problems until I came across a setting which (I think) stopped it from doing something stupid like disappearing off and checking all dependencies or something like that. I've checked the options and I can't see anything like that. I have plenty of available memory on my machine (400Mb plus) so it's not a swapping issue. I'm also not running anything "complicated" like a DB connection, although I do occasionally use the built-in Tomcat 5.0 for JSPs and Servlets. I have no network and there are no other heavy tasks going on at the same time (other apps work fine while Netbeans goes AWOL).
Does anyone know how to stop Netbeans from doing this, or where it disappears off to (i.e. why it does it)? I'd appreciate any pointers other than "use Eclipse" which, without a solution, will be my next stop.
I think I've figured out that the cause of Netbean's slowness is the Swing. Maybe it's doing some stuff it shouldn't be in the event dispatch thread. Maybe is calls Swing.snooze() every now and then! Anyway, it can particularly take ages (up to a couple of minutes) when switching between windows, say from IE.
Does Eclipse suffer from the same intolerable crapness? I used it for about a month a year or so ago but I can't remember. Any free IDE that doesn't make you want to put your fist through the screen?
I was a longtime fan of NetBeans -- even from back when it was called Forte For Java! Almost 3 years ago (in NB2.0!) I ran into the same issues that you discuss in that it would suddenly pause, ostensibly for a gc run (that's what it feels like, anyway). I got so frustrated I quit using it... and that's when I discovered Eclipse.
Eclipse is of course not swing -- it is SWT. Native. Fast. Stable. It was like I'd gone to heaven.
With the recent release of NB4, I had hoped they had fixed the issue. With your complaint on NB 3.6, my hopes have suddenly diminished greatly.
My advice is to dump NB and visit Eclipse.org.
"Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster." --The JavaPerformanceTuning.com team, Newsletter 039.
Joined: Aug 02, 2004
Thanks folks. That's exactly the sort of feedback I was looking for.
I think I'll take your advice and switch to Eclipse.