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 35164 - Memory leak and slow degugging
Summary: Memory leak and slow degugging
Status: CLOSED INVALID
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: ARCH, PERFORMANCE
Depends on:
Blocks:
 
Reported: 2003-07-28 11:56 UTC by jd
Modified: 2010-04-29 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jd 2003-07-28 11:56:47 UTC 
I'm experiencing big difficulties while debugging.
NB seams to freeze (while the application continue
working). while ui take a long to repaint
sometimes breakpoint are skipped.
I was debugging a trivial program.

ide.cfg contains

-J-Xms64m -J-Xmx256m
-J-Xverify:none
Comment 1 kovica 2003-07-29 00:07:56 UTC 
I'm also experiencing this on Mandrake 9.1 and with Sun JDK 1.4.2, Sun
JDK 1.4.1 and Blackdown JDK 1.4.1
Comment 2 spl 2003-10-23 03:20:02 UTC 
I also have Netbeans "die" when grading small programs. The GUI can
takes minutes to redraw and then still be unresponsive to mouse input.

I have also notice using the memeory tool bar that there is a memory
leak while Netbeans 3.5.1 is just sitting on my Windows 2000 (service
pack 4) desktop. Looking at the Windows Task Manager I notice that
Netbeans has 1,357 handles. Seems like a veru large number. Mozillas
only has 290 with several windows and tabs open.
Comment 3 Maros Sandor 2004-01-05 16:03:22 UTC 
Can you verify these issues still exist in 3.6 development version? 
If so, please describe what steps lead to these frozen/unusable 
states. Be specific about your HW and SW configuration, programs you 
debug (ideally attach sources with a test case) so we may reproduce 
your problems here a fix it. Marking as incomplete until we get 
enough information to reproduce it. Skipping of breakpoints seem to 
be a serious problem, please try to reproduce that as well. (Note 
that any Swing program uses lots of handles.)
Comment 4 Jan Jancura 2004-05-31 13:13:55 UTC 
closing incomplete bug
Comment 5 Quality Engineering 2010-04-29 09:14:22 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.