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.
Summary: | The system aborts when File menu selected | ||
---|---|---|---|
Product: | platform | Reporter: | Ivana Ladenbergerova <iladenbergerova> |
Component: | -- Other -- | Assignee: | Pavel Buzek <pbuzek> |
Status: | CLOSED WONTFIX | ||
Severity: | normal | CC: | sdennie |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | Sun | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | IDE.log |
Description
Ivana Ladenbergerova
2001-02-06 13:17:23 UTC
Created attachment 577 [details]
IDE.log
This is a HotSpot bug, report it to the JDK team. Leaving this open until this bug report is updated with the BugTraq number of the bug that was reported to the JDK team. **Obviously** we are not just going to close this report by stating that it is someone else's problem. **Clearly**, the most basic requirement is that we at least tell the other person or team. Also, given that the JVM FAQ states that it "highly recommends" the 1.3 virtual machine where HotSpot is turned on by default, just stating that this is someone else's problem and walking away is totally unacceptable. Changing to P1. We can't have the File menu item processing abort in the recommended configuration and leave this as a P4. Pavel, who should report it to JDK team? Reproducible and I got following message: # # HotSpot Virtual Machine Error, Unexpected Signal 11 # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error happened during: scavenge # # Error ID: 4F533F534F4C415249530E435050079A 01 # # Problematic Thread: prio=5 tid=0xa0e78 nid=0x4 runnable # When searching the BugParade on JDC, I have found large numbers of bugs with the same Error ID. Most of them are fixed in 1.3.1 LadyBird. I checked the above described behaviour using jdk1.3.1 (Java HotSpot(TM) Client VM 1.3.1-rc1-b21) and Forte4JCE2.0 and NetBeans3.2-RC2 and the bug does not occurs anymore. So as workaround use jdk1.3.1, and I am going to close this bug as won't fix and add link to the JDC. For more infos check: http://developer.java.sun.com/developer/bugParade/bugs/4408730.html Resolved for 3.4.x or earlier, no new info since then -> verified. Resolved for 3.4.x or earlier, no new info since then -> closing. |