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 42527 - 100% CPU after terminating a JSP debugging session
Summary: 100% CPU after terminating a JSP debugging session
Status: VERIFIED WORKSFORME
Alias: None
Product: javaee
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-04-27 16:58 UTC by cgriswold
Modified: 2005-12-14 14:40 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Console thread dump (12.16 KB, text/plain)
2004-04-27 16:59 UTC, cgriswold 		Details
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 cgriswold 2004-04-27 16:58:00 UTC 
When I terminate a JSP debugging session by
stopping the debugger on the main task bar, the
CPU goes to 100%.  The windows process monitor
shows a java.exe at 98% cpu. If I stop Tomcat, I
see runide at 98%. I have to restart NetBeans to
clear the problem.
A console dump is attached.
Comment 1 cgriswold 2004-04-27 16:59:36 UTC 
Created attachment 14588 [details]
Console thread dump
Comment 2 Martin Grebac 2004-05-05 09:24:43 UTC 
Hmm, I assume you use the default shared memory transfer for debugging
- could you please try to use socket transfer? (stop tomcat, change
debug mode of the server instance to dt_socket).
Comment 3 Martin Grebac 2004-05-21 16:16:41 UTC 
I can't reproduce and have no further info from the submitter (socket
transfer try, jdk version). Closing as works for me - please reopen
with additional info.
Comment 4 Jiri Skrivanek 2005-12-14 14:40:25 UTC 
No other feedback, so verifying as worksForMe.