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 231193 - IllegalStateException: Invalid thread state NEW for taking a stack trace
Summary: IllegalStateException: Invalid thread state NEW for taking a stack trace
Status: RESOLVED DUPLICATE of bug 231152
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-13 08:40 UTC by Egor Ushakov
Modified: 2013-06-13 09:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 201378


Attachments
stacktrace (4.27 KB, text/plain)
2013-06-13 08:40 UTC, Egor Ushakov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Egor Ushakov 2013-06-13 08:40:51 UTC
Build: NetBeans IDE Dev (Build 201306102301)
VM: Java HotSpot(TM) Client VM, 23.21-b01, Java(TM) SE Runtime Environment, 1.7.0_21-b11
OS: SunOS

User Comments:
gorrus: opened a snapshot




Stacktrace: 
java.lang.IllegalStateException: Invalid thread state NEW for taking a stack trace
   at org.netbeans.lib.profiler.results.cpu.StackTraceSnapshotBuilder.processDiffs(StackTraceSnapshotBuilder.java:385)
   at org.netbeans.lib.profiler.results.cpu.StackTraceSnapshotBuilder.processThreadDump(StackTraceSnapshotBuilder.java:350)
   at org.netbeans.lib.profiler.results.cpu.StackTraceSnapshotBuilder.addStacktrace(StackTraceSnapshotBuilder.java:319)
   at org.netbeans.modules.profiler.LoadedSnapshot.loadSnapshotFromStackTraces(LoadedSnapshot.java:250)
   at org.netbeans.modules.profiler.LoadedSnapshot.loadSnapshot(LoadedSnapshot.java:236)
   at org.netbeans.modules.profiler.ResultsManager.loadSnapshotFromFileObject(ResultsManager.java:1148)
Comment 1 Egor Ushakov 2013-06-13 08:40:52 UTC
Created attachment 135738 [details]
stacktrace
Comment 2 Egor Ushakov 2013-06-13 09:10:59 UTC

*** This bug has been marked as a duplicate of bug 231152 ***