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 101815

Summary: Assertion failed in ..\src-jdk15\class-file-cache.c
Product: profiler Reporter: Alexander Kouznetsov <mrkam>
Component: BaseAssignee: issues@profiler <issues>
Status: VERIFIED DUPLICATE    
Severity: blocker    
Priority: P2    
Version: 6.x   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Attachments: screenshot
Dump

Description Alexander Kouznetsov 2007-04-19 17:23:09 UTC 
Profiler 070417
NetBeans IDE Dev (Build 070418)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251

Steps to reproduce:
- Start Tomcat 5.5
- Invoke Attach Wizard
- Select <External Application>, CPU Profiling, Entire Application, Profile All
Classes
- Define Local Dynamic Attach mode
- Try to Attach
- RESULT: Assertion failed in ..\src-jdk15\class-file-cache.c Microsoft Visual
C++ Runtime Library dialog is shown and Tomcat is terminated with the following
info:

#
# An unexpected error has been detected by Java Runtime Environment:
#
#  EXCEPTION_INT_DIVIDE_BY_ZERO (0xc0000094) at pc=0x10003038, pid=3232, tid=200
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode)
# Problematic frame:
# C  [profilerinterface.dll+0x3038]
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Comment 1 Alexander Kouznetsov 2007-04-19 17:23:52 UTC 
Created attachment 41275 [details]
screenshot
Comment 2 Alexander Kouznetsov 2007-04-19 17:24:46 UTC 
Created attachment 41276 [details]
Dump
Comment 3 Tomas Hurka 2007-04-26 12:31:35 UTC 

*** This issue has been marked as a duplicate of 100641 ***
Comment 4 Alexander Kouznetsov 2007-04-26 14:30:17 UTC 
The assertion dialog is the same, while the JVM crash is different. Could you
please clarify why this issue should be a duplicate?
Comment 5 Tomas Hurka 2007-04-27 08:50:23 UTC 
From 'man assert' :
The assert() macro tests the given expression and if it is false, the calling process is terminated.  

So it is irrelevant what happened after the assert, the JVM should end. 

*** This issue has been marked as a duplicate of 100641 ***
Comment 6 Alexander Kouznetsov 2007-04-27 08:58:31 UTC 
OK, verified