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 8563 - any other java application (e.g. running debugger) crashes F4J
Summary: any other java application (e.g. running debugger) crashes F4J
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-11-26 07:05 UTC by Wayne Robin Isaacs, Jr.
Modified: 2008-12-23 10:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Wayne Robin Isaacs, Jr. 2000-11-26 07:05:42 UTC 
setup: Multi-processor Win2kAdvSrv, intel p3X2 @1ghz; JDK1.2, ffj 1.0 release 2

1. run F4J
2. run any java application, either from the debugger or command-prompt.
3. a) before terminating second application, return focus to F4J
OR
b) terminate second application

result: F4J crashes with inaccessible memory error.  When the crash
notification screen appears, mouse pointer is disabled (invisible) for all
windows associated with F4J.

If scenario 3.a) is used, the second application also crashes with access
violation.

Thus, using the debugger always crashes F4J; sometimes on entry, sometimes on
exit.  No examples can be tested, although they run if F4J is not loaded.
Comment 1 Jesse Glick 2000-11-27 16:35:59 UTC 
Java virtual machine bug (which should be reported to the JDK team), not an IDE
bug, if the VM crashes.

Strongly suggest upgrading to JDK 1.3 FCS.

This kind of thing you may want to bring up on nbusers@netbeans.org to see if
anyone else has had the same experience. If it turns out that (1) the problem is
really reproducible on unrelated machines with a certain kind of configuration
and (2) there is some definite action in the IDE which triggers it, then it may
be possible to implement a workaround which sidesteps the bug. Regardless, it
should be reported to the VM people.

You might try using green vs. native threads, or fiddling with other VM
parameters, to see if they have any effect. But upgrade to 1.3 first.
Comment 2 Quality Engineering 2003-07-01 16:04:22 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 3 Quality Engineering 2003-07-01 16:28:53 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.