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 131016 - EXCEPTION_ACCESS_VIOLATION when run MediaExample project
Summary: EXCEPTION_ACCESS_VIOLATION when run MediaExample project
Status: VERIFIED WONTFIX
Alias: None
Product: javafx
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: cms
URL:
Keywords: RELNOTE
Depends on:
Blocks:
 
Reported: 2008-03-25 12:55 UTC by Alexandr Scherbatiy
Modified: 2008-06-03 10:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
MediaExample project (21.59 KB, application/octet-stream)
2008-03-25 12:57 UTC, Alexandr Scherbatiy
Details
Profiler log file (9.60 KB, text/plain)
2008-03-25 12:58 UTC, Alexandr Scherbatiy
Details
IDE log file (36.53 KB, text/plain)
2008-04-23 12:27 UTC, Alexandr Scherbatiy
Details
Profiler hs_err_pid file (8.82 KB, text/plain)
2008-04-23 12:28 UTC, Alexandr Scherbatiy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Scherbatiy 2008-03-25 12:55:09 UTC
Steps to reproduce:

- Download attached MediaExample project
- Download JMF library from
  http://java.sun.com/products/java-media/jmf/2.1.1/download.html 
- Open the MediaExample  project and resolve broken links
- Profile the MediaExample  project

 The EXCEPTION_ACCESS_VIOLATION appears in the output window

Profiler Agent: Waiting for connection on port 5140, timeout 10 seconds (Protocol version: 8)
Profiler Agent: Established local connection with the tool
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d945e13, pid=2436, tid=3912
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_05-ea-b04 mixed mode windows-x86)
# Problematic frame:
# V  [jvm.dll+0x95e13]
#
# An error report file with more information is saved as:
Profiler Agent: Initializing...
Profiler Agent: Options: >C:\Program Files\netbeans\profiler3\lib,5140,10<
Profiler Agent: Initialized succesfully
Profiler Agent: Redefining 100 classes at idx 0, out of total 552 
Profiler Agent: Redefining 100 classes at idx 100, out of total 552
Comment 1 Alexandr Scherbatiy 2008-03-25 12:57:29 UTC
Created attachment 59005 [details]
MediaExample project
Comment 2 Alexandr Scherbatiy 2008-03-25 12:58:23 UTC
Created attachment 59006 [details]
Profiler log file
Comment 3 Alexandr Scherbatiy 2008-03-26 10:06:17 UTC
Additional steps:

- Profile the MediaExample  project in CPU mode
- Switch the project profiling to Memory mode

The exception appears. 
Comment 4 Alexandr Scherbatiy 2008-04-10 09:08:08 UTC
See issue 113847 and bug in JDK http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6598065
Comment 5 cms 2008-04-15 13:03:23 UTC
According to evaluations of issues mentioned above, this is a JDK issue. Can't be fixed in JavaFX Profiler itself. The
suggested work-around is to run profiled application with -Xshare:off.
Comment 6 Alexei Mokeev 2008-04-15 13:11:20 UTC
Let's make sure that it is documented on Wiki
Comment 7 cms 2008-04-15 13:41:10 UTC
Created JavaFX plugin "Known Issues" wiki page: http://wiki.netbeans.org/JavaFXPluginKnownIssues. 
Comment 8 Alexandr Scherbatiy 2008-04-23 12:26:24 UTC
I added -Xshare:off options to the project VM options but the issue is still reproduced:
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d945e13, pid=1620, tid=1472
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_05-ea-b04 mixed mode windows-x86)
# Problematic frame:
# V  [jvm.dll+0x95e13]
#
# An error report file with more information is saved as:
# C:\Documents and Settings\andromeda\My Documents\NetBeansProjects\temp\75\JavaFXApplication2\hs_err_pid1620.log
#
# If you would like to submit a bug report, please visit:
Profiler Agent: Initializing...
Profiler Agent: Options: >C:\Program Files\nb\netbeans\profiler3\lib,5140,10<
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Profiler Agent: Initialized succesfully
Profiler Agent: Redefining 100 classes at idx 0, out of total 552 
Profiler Agent: Redefining 100 classes at idx 100, out of total 552 
Profiler Agent: Redefining 100 classes at idx 200, out of total 552 
Profiler Agent: Redefining 100 classes at idx 300, out of total 552 
Profiler Agent: Redefining 100 classes at idx 400, out of total 552 
Profiler Agent: Redefining 52 classes at idx 500, out of total 552 
Java Result: 1
Comment 9 Alexandr Scherbatiy 2008-04-23 12:27:25 UTC
Created attachment 60600 [details]
IDE log file
Comment 10 Alexandr Scherbatiy 2008-04-23 12:28:36 UTC
Created attachment 60601 [details]
Profiler hs_err_pid file
Comment 11 Alexandr Scherbatiy 2008-05-01 10:40:40 UTC
The issue is reproduced with jdk 1.6.0_05
and is not reproduced with jdk1.6.0_10
Comment 12 cms 2008-05-04 10:45:25 UTC
Can't reproduce with jdk 1.6.0_10 either. Looks like this is a side effect of some VM improvement. Note that jdk
1.6.0_05 uses HotSpot VM 10.0-b19 when jdk 1.6.0_10 uses HotSpot VM 11.0-b11. Have nothing to do with this in scopes of
JavaFX Profiler module. The recommendation to use jdk 1.6.0_10 or later for JavaFX projects profiling will be added to Wiki.
Comment 13 Alexandr Scherbatiy 2008-06-03 10:21:28 UTC
verified with JDK 6 update 10