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 198376 - while debugging after some time netbean taking 50-60% CPU usage and Slow donw
Summary: while debugging after some time netbean taking 50-60% CPU usage and Slow donw
Status: RESOLVED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.0
Hardware: PC Windows XP
: P1 normal (vote)
Assignee: Martin Entlicher
URL: http://localhost:8080
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-06 11:14 UTC by raviparekh
Modified: 2011-05-10 09:40 UTC (History)
0 users

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 raviparekh 2011-05-06 11:14:21 UTC
while debugging my web application and more on JSP page netbeans 7.0 Slow too much and takes 50-60% of CPU.

to finish i have to kill netbeans and java.exe that was for debugging


netbeans.exe is using 607K

in log file i got java HEAP SPACE
MY Configuration is 

intel Core 2 duo 2.93 GHz
3.24 GB of RAM
XP SP3
Comment 1 Martin Entlicher 2011-05-06 11:25:05 UTC
This can be a duplicate of issue #197158. Can you please try a recent dev build from http://bits.netbeans.org/dev/nightly/latest/ to see if the problem persists?
Thank you.
Comment 2 raviparekh 2011-05-06 11:26:14 UTC
this happens because it remain started for 2 Hours but no process no Request and after 2 hours i started debugging. on simple jsp with update/Add it started consuming memory in fact it consumed memory and begun consuming more memory.

i added in netbean.config

-J-Xmx

(heap) and

-J-XX:MaxPermSize

but i don't think so my JSP needs so much of memory for this

i started th profile the IDE but unable to save cause killing the netbean 7.
Comment 3 Martin Entlicher 2011-05-06 11:32:48 UTC
Can you please take a heap dump when this happens?
It can be done via jmap -dump:format=b,file=heap.bin PID
where PID is the process ID that you can get by jps.
jps should print something like:
4898 Jps
4408 Main
in this case PID is 4408.
Comment 4 Martin Entlicher 2011-05-10 09:40:18 UTC
Please provide the heap dump, so that we can find out what is consuming the memory. Thank you.