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 233301 - JVM Crash when monitoring lock contention
Summary: JVM Crash when monitoring lock contention
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 7.4
Hardware: PC Linux
: P2 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-24 10:12 UTC by J Bachorik
Modified: 2013-07-25 02:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
HS_ERR (40.75 KB, text/x-log)
2013-07-24 10:12 UTC, J Bachorik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description J Bachorik 2013-07-24 10:12:26 UTC
Created attachment 137679 [details]
HS_ERR

Running an extensive profiling (profile all classes) together with lock contention monitoring can lead to JVM crash.

The generated dump file is in the attachment.
Comment 1 Tomas Hurka 2013-07-24 13:48:14 UTC
Fixed in profiler-main

changeset:   259155:4b6afd8c525a
user:        Tomas Hurka <thurka@netbeans.org>
date:        Wed Jul 24 15:46:35 2013 +0200
summary:     bugfix #233301, ignore profiler server own monitor(s) in monitorEntry() and monitorExit()
Comment 2 J Bachorik 2013-07-24 14:09:36 UTC
Crash does not happen any more.
Comment 3 Quality Engineering 2013-07-25 02:27:27 UTC
Integrated into 'main-silver', will be available in build *201307242300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/4b6afd8c525a
User: Tomas Hurka <thurka@netbeans.org>
Log: bugfix #233301, ignore profiler server own monitor(s) in monitorEntry() and monitorExit()