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 146914 - [65cat] Debugger causes kill of IDE
Summary: [65cat] Debugger causes kill of IDE
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on: 145255
Blocks:
  Show dependency tree
 
Reported: 2008-09-11 11:52 UTC by ulfzibis
Modified: 2008-09-17 10:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
breakpoint setting (69.18 KB, image/jpeg)
2008-09-11 11:54 UTC, ulfzibis
Details
log files (79.63 KB, application/x-compressed)
2008-09-11 12:02 UTC, ulfzibis
Details
hs_err (18.12 KB, text/plain)
2008-09-11 15:34 UTC, Peter Pis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ulfzibis 2008-09-11 11:52:34 UTC
[ BUILD # : 200809101401 ]
[ JDK VERSION : 1.6.0 ]

[JDK 1.6.0_10 RC]
- Checkout this project (by revision 396!):
https://java-nio-charset-enhanced.dev.java.net/source/browse/java-nio-
charset-enhanced/trunk/?rev=396
- ensure you have 2nd JDK (e.g. 1.6.0 b105) installed on your system
and resolve broken link from Project Properties.
- set breakpoint as shown in attachment
- "Debug File" CharsetsTest
- wait for some minutes
--> NetBeans GUI will disappear without notice. Sometimes you will
see java.exe=100% CPU in Windows Taskmanager. After a while it will
disappear also.
Comment 1 ulfzibis 2008-09-11 11:54:38 UTC
Created attachment 69634 [details]
breakpoint setting
Comment 2 ulfzibis 2008-09-11 12:02:42 UTC
Created attachment 69639 [details]
log files
Comment 3 Martin Entlicher 2008-09-11 12:51:33 UTC
If JVM disappears it's a defect of the JVM.
Any error dump files from JVM?

Will try the described use-case...
Comment 4 ulfzibis 2008-09-11 13:29:13 UTC
Dead of IDE was 2..3 minutes before the dead of java.exe.
At my 2nd try (to assure it's reproducible) I couldn't find any java.exe in task manager after dead of IDE. Maybe cause
of the fact, that NB was just freshly started.
(At normal run I see 2 java.exe, because my project uses alternative JDK)

How to save error dump files from JVM? Can you give me short advice.
I started IDE from Start Menu; JVM's were started by NB.


Comment 5 Petr Cyhelsky 2008-09-11 13:48:23 UTC
java error logs are files with name like: hs_err_pid*.log where the asterisk is pid of the crashed process. They are
located in the directory with the program which crashed, so in your case either in your netbeans directory or
netbeans/bin directory.
Comment 6 Martin Entlicher 2008-09-11 14:22:27 UTC
I'm sorry, but I can not get the sources. The following command asks for password:
svn checkout https://java-nio-charset-enhanced.dev.java.net/svn/java-nio-charset-enhanced/trunk -r 396
java-nio-charset-enhanced

Is there a way how to retrieve the code anonymously?
Or can you either attach zipped sources here or (if it's too big) send it to my e-mail mentlicher@netbeans.org? Thanks.
Comment 7 Martin Entlicher 2008-09-11 14:25:08 UTC
Please forget about it, I've just found a "guest" user name with an empty password. I'm just downloading the sources...
Comment 8 Martin Entlicher 2008-09-11 15:02:13 UTC
On Linux it works fine, nothing disappears.
Peter, can you please check on Windows?
Comment 9 Peter Pis 2008-09-11 15:33:33 UTC
Reproduced on Windows. But this is a jdk problem. Ulf, could you please report it?

http://java.sun.com/webapps/bugreport/crash.jsp
Comment 10 Peter Pis 2008-09-11 15:34:37 UTC
Created attachment 69666 [details]
hs_err
Comment 11 ulfzibis 2008-09-11 20:49:27 UTC
> Is there a way how to retrieve the code anonymously?
Sorry, I assumed, you were familiar with java.net projects. The anonymous checkout could always be found at menu item
"Subversion", here:
https://java-nio-charset-enhanced.dev.java.net/source/browse/java-nio-charset-enhanced/
Comment 12 Petr Cyhelsky 2008-09-16 21:22:50 UTC
This issue seems to have the same root cause as Issue #145255 - the problem is created by output window allocating too
much memory. 
Comment 13 Petr Cyhelsky 2008-09-16 21:24:00 UTC
The problem is fixed by fixing of Issue #145255
Comment 14 ulfzibis 2008-09-16 23:16:10 UTC
I tried to reproduce it with Build 200809130201.

Happy, the error didn't occur. The debug session ran ~10 minutes without problems, until I stopped it. :-)
So this issue seems to be resolved, regardless it's caused by JDK bug.
Comment 15 ulfzibis 2008-09-16 23:20:13 UTC
I have news from JDK's bug parade:

We have determined that this report is a new bug and entered the bug into our internal bug tracking system under Bug Id:
6748784.

You can monitor this bug on the Java Bug Database at
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6748784.