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 5854 - IDE always freezes during debugging session.
Summary: IDE always freezes during debugging session.
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P2 normal (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-02-24 02:04 UTC by L Martinek
Modified: 2008-12-23 10:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
thread dump (13.15 KB, text/plain)
2000-08-23 16:02 UTC, Daniel Prusa
Details
thread dump (JPDA started instead of Tools debugger) (17.15 KB, text/plain)
2000-08-23 16:03 UTC, Daniel Prusa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description L Martinek 2000-02-24 02:04:26 UTC
Occurs only in Windows 98 and Windows 2000 with JDK 1.3 (with or without hotspot).


Try this to reproduce:

- Create new class from template: Classes | Main
- Add this code into main():
     System.out.println("Ahoj");
     int i;
     i=10;
     System.out.println(i);
     int x=20;
     System.out.println(x);
- Compile it, set breakpoint on first line of main method. Press F5.
- Trace over utill you will be on line with "System.out.println(i);"
- Add variable i to watches.
- Trace over to last line in main method. Add variable x to watches.

This is not only one way to freeze IDE and it is not necessary to add watches. This is only my procedure  to freeze IDE during debugging that always works.

Thread dump is in attachment.
Thread dump for debugging with JPDA added to attachment.

[Dan]
Occurs when focus is changed (from editor to debugger window).
Comment 1 David Simonek 2000-08-23 15:44:59 UTC
Thread dump is missing, without it I cannot do anything with this bug now.
Moreover, I still think the bug is related to debugger and it is debugger
team's responsibility to fix it. (or maybe it is obsolete now, I don't know)
Comment 2 Daniel Prusa 2000-08-23 16:02:59 UTC
Created attachment 108 [details]
thread dump
Comment 3 Daniel Prusa 2000-08-23 16:03:59 UTC
Created attachment 109 [details]
thread dump (JPDA started instead of Tools debugger)
Comment 4 L Martinek 2000-08-23 16:16:59 UTC
Now I can't reproduce this bug. It's maybe fixed.
Libor