This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 144187 - NetBeans 6.5 Beta Pretty Much Unusable
Summary: NetBeans 6.5 Beta Pretty Much Unusable
Status: RESOLVED DUPLICATE of bug 145464
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker with 1 vote (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-16 22:48 UTC by willfarnaby
Modified: 2008-10-17 06:14 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description willfarnaby 2008-08-16 22:48:54 UTC
Using the NetBeans 6.5 Beta, I've come to the conclusion that the NetBeans IDE has become Pretty Much Unusable.

I'm using a realistic set of projects, on a pretty good workstation, with a 768M max heap, running GlassFish v2u2, and
even with "Deploy On Change" turned off (which seems necessary when making changes to code with any sort of frequency),
the teeth-grinding waits due to the often mostly / completely unresponsive UI (sometimes I even have to kill the IDE
process) have led me to download MyEclipseIDE and contemplate migrating to Eclipse over there. (This in spite of the
fact that I like NetBeans and, especially, the progress of the NetBeans Platform (although I'm working on J2EE / EJB /
Web Services, not Swing at this time).

Is such terminal unusability being addressed for 6.5 Final ???
Comment 1 willfarnaby 2008-08-16 23:03:00 UTC
To be clear : if I was just using NetBeans as a "word processor", it'd be ok, but using it for software development -
with a REAL-WORLD set of projects, where cleaning, compilations and building occur, with interdependencies... its
performance is generally terrible.
Comment 2 willfarnaby 2008-08-16 23:56:15 UTC
...It's performance is generally terrible... due to "Scanning...", "Compiling...", and various other, background
processing tasks.
Comment 3 Tomas Danek 2008-08-27 11:38:38 UTC
If you spot ide iresponsiveness, could you please generate thread-dump? it will show the culprit..
http://wiki.netbeans.org/GenerateThreadDump Thanks.
Comment 4 willfarnaby 2008-08-27 21:47:06 UTC
Yes, indeed I shall.
Comment 5 Vince Kraemer 2008-08-27 22:25:22 UTC
without any specific data to analyze or description of steps to reproduce the offending behavior, I don't know how an
engineer will be able to claim that they have fixed this issue.

once the filer adds more details, somebody could probably make progress on this.
Comment 6 willfarnaby 2008-08-28 01:10:03 UTC
Of course, I will try to provide additional specifics (working in Visual Studio at the moment).

Yet, as this long thread on netbeans-user discusses at length, surely the developers responsible for NetBeans must also
suffer pain from due to various background tasks at various times killing performance and usability... ?!

[quote]

------- Additional comments from willfarnaby Sat Aug 16 22:56:15 +0000 2008 -------

...It's performance is generally terrible... due to "Scanning...", "Compiling...", and various other, background
processing tasks.

------- Additional comments from vkraemer Wed Aug 27 21:25:22 +0000 2008 -------

without any specific data to analyze or description of steps to reproduce the offending behavior, I don't know how an
engineer will be able to claim that they have fixed this issue.

once the filer adds more details, somebody could probably make progress on this.

[/quote]
Comment 7 David Konecny 2008-09-01 21:02:21 UTC
Very likely duplicate of 145464. Feel free to reopen if you disagree and attach details/thread dumps. Thanks.

*** This issue has been marked as a duplicate of 145464 ***
Comment 8 _ hong_lin 2008-10-17 06:14:09 UTC
willfarnaby,

This issue was marked as duplicate of issue 145464, which is also a duplicate of issue 145546.

issue 145546 was fixed and was verified by its issue reporter in build 20081007.

Would you like to try a build later than 20081007, see if your problem is solved as well?

Thanks,
Hong