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 7076 - IDE crashes with EXCEPTION_ACCESS_VIOLATION in native code
Summary: IDE crashes with EXCEPTION_ACCESS_VIOLATION in native code
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 major (vote)
Assignee: anovak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-07-17 10:44 UTC by Jan Chalupa
Modified: 2008-12-22 17:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Log 1 (5.01 KB, text/plain)
2001-07-20 20:46 UTC, Jan Chalupa 		Details
Log 2 (192 bytes, text/plain)
2001-07-20 20:46 UTC, Jan Chalupa 		Details
Dr. Watson Log (32.08 KB, text/plain)
2001-07-20 20:46 UTC, Jan Chalupa 		Details
Excerpt from Dr. Watson log (33.12 KB, text/plain)
2001-08-23 16:10 UTC, gthb 		Details
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 Jan Chalupa 2000-07-17 10:44:15 UTC 
Sometimes, the JVM crashes with the "EXCEPTION_ACCESS_VIOLATION detected in
native code" message during start of the IDE.

See the attached log files.
Comment 1 Jan Chalupa 2000-07-17 10:46:59 UTC 
Created attachment 36 [details]
Log 1
Comment 2 Jan Chalupa 2000-07-17 10:47:59 UTC 
Created attachment 38 [details]
Dr. Watson Log
Comment 3 anovak 2000-08-02 15:27:59 UTC 
The bug is in fact in ZipFile.java
This is workaround only.
Comment 4 Jan Chalupa 2001-04-27 17:10:40 UTC 
Verified - the workaround works.
Comment 5 gthb 2001-08-23 16:08:12 UTC 
I just obtained this native exception with a fresh install of
3.2.1 while running a small test app in the debugger. The test
app does not contain any native code.

Since this issue never had a precise description of the
circumstances leading to the exception, I guess it's
appropriate to reopen this one rather than submit a new one. 

I will attach the portion of my DrWatsonLog.txt that describes
this bug. Search for FAULT to find the problem (it's inside a
series of !<nosymbols> stack frames, so good luck tracking it
down! :)
Comment 6 gthb 2001-08-23 16:10:20 UTC 
Created attachment 2287 [details]
Excerpt from Dr. Watson log
Comment 7 gthb 2001-08-23 16:13:29 UTC 
Updated version and OS to describe
the setup I encountered this on.
Comment 8 gthb 2001-08-23 16:30:19 UTC 
I get the crash consistently if I have a breakpoint in my
code, do not get the crash if I remove the breakpoint.
This happens for several different locations of the
breakpoint, but not all locations. When I place the
breakpoint far enough earlier in the execution, it breaks
successfully, but when I then single-step through the code,
an access violation exception is thrown at a later point,
but it is not the same one (not at the same address, and the
particular null-pointer-based address is 0x00000010 instead
of 0x00000083 in the previous case).

The test program I'm debugging is not something I can
release. If so requested, I can try to isolate the problem
in a small test case and submit it.
Comment 9 anovak 2001-09-10 11:14:15 UTC 
This is apparently a problem with JDK. If possible create a small test
case and send it to BugParade on java.sun.com
Comment 10 Quality Engineering 2003-07-01 15:52:43 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 11 Quality Engineering 2003-07-01 16:17:39 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.