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 14825

Summary:	IDE blocked after Step over
Product:	debugger	Reporter:	pgodeau <pgodeau>
Component:	Java	Assignee:	issues@debugger <issues>
Status:	CLOSED DUPLICATE
Severity:	blocker
Priority:	P3
Version:	3.x
Hardware:	PC
OS:	Windows 3.1/NT
Issue Type:	DEFECT	Exception Reporter:
Attachments:	ide.log

Description pgodeau 2001-08-27 15:45:40 UTC

Very often, after pressing F8 (step over) the IDE hangs and is blocked.
It seems to happen at random times, but almost on every debug session.
The strange thing is that nothing responds, and the runide process
is not active (0% CPU).
The only option is to kill the java.exe process, then IDE is active again.
Any help is welcome, thanks.

Comment 1 pgodeau 2001-08-27 15:46:44 UTC

Created attachment 2309 [details]
ide.log

Comment 2 pgodeau 2001-08-28 16:26:35 UTC

After some investigation, it appears that it works much better
with debugger's Classic switch set to True.
Could you explain this?

Comment 3 Daniel Prusa 2001-08-29 14:40:57 UTC

If debugger's Classic switch is set to True, the debugged application 
is runned on Classic VM (not HopSpot). According to my experiences, 
to debug Classic VM is more reliable (however, the debugee can run 
slowly, in addition, Classic VM is not supported since JDK 1.4, thus 
Classic switch is set to false defaultly).

To investigate your problem, it could be helpful to see thread dump 
of the blocked IDE. How to obtain it:
1) Start IDE using netbeans\bin\runide.exe (Command Window is opened).
2) Force IDE to hang.
3) Focus Command Window, press CTRL+Break. Thread dump is printed.
Can you perform these steps and attach the thread dump, please ?

Comment 4 Daniel Prusa 2001-09-06 17:23:25 UTC

It is the same sort of problems as described in issue 13953.

*** This issue has been marked as a duplicate of 13593 ***

Comment 5 Daniel Prusa 2001-09-06 17:30:32 UTC

Wrong resolution, it is duplicate of 13953, not 13593. My fingers are 
sometimes too fast, sorry.

Comment 6 Daniel Prusa 2001-09-06 17:32:02 UTC


*** This issue has been marked as a duplicate of 13953 ***

Comment 7 Jan Stola 2001-09-07 14:24:35 UTC

Duplicate -> Closed.