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 206494 - org.netbeans.lib.profiler.client.ClientUtils$TargetAppOrVMTerminated: Target JVM inactive
Summary: org.netbeans.lib.profiler.client.ClientUtils$TargetAppOrVMTerminated: Target ...
Status: RESOLVED INCOMPLETE
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: J Bachorik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-17 06:49 UTC by akochnev
Modified: 2012-04-18 17:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 183872


Attachments
stacktrace (836 bytes, text/plain)
2011-12-17 06:49 UTC, akochnev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description akochnev 2011-12-17 06:49:30 UTC
This bug was originally marked as duplicate of bug 205287, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 20111210-6a38df8032ae)
VM: OpenJDK 64-Bit Server VM, 20.0-b11, OpenJDK Runtime Environment, 1.6.0_23-b23
OS: Linux

User Comments:
akochnev: trying to terminate a profiling session




Stacktrace: 
org.netbeans.lib.profiler.client.ClientUtils$TargetAppOrVMTerminated: Target JVM inactive
   at org.netbeans.lib.profiler.ProfilerClient.checkForTargetVMAlive(ProfilerClient.java:1520)
   at org.netbeans.lib.profiler.ProfilerClient.getCPUProfilingResultsSnapshot(ProfilerClient.java:492)
   at org.netbeans.modules.profiler.ResultsManager.prepareSnapshot(ResultsManager.java:744)
   at org.netbeans.modules.profiler.ResultsManager.prepareSnapshot(ResultsManager.java:719)
   at org.netbeans.modules.profiler.ResultsManager.takeSnapshot(ResultsManager.java:887)
   at org.netbeans.modules.profiler.ProfilerControlPanel2$ResultsSnippetPanel$2.run(ProfilerControlPanel2.java:773)
Comment 1 akochnev 2011-12-17 06:49:32 UTC
Created attachment 114283 [details]
stacktrace
Comment 2 J Bachorik 2012-04-18 14:10:39 UTC
Seems like you have tried to obtain a profiler snapshot before terminating the session. Can you provide some steps to reproduce?
Comment 3 akochnev 2012-04-18 15:41:21 UTC
I don't have any further steps to reproduce. Even if I did something unexpected/invalid (e.g. tried obtaining a snapshot before terminating the session) it seems that at least the exception should be handled more gracefully
Comment 4 J Bachorik 2012-04-18 17:41:43 UTC
Actually, the exception is caught and logged. But the Level.SEVERE seems to force the IDE to display the exception dialogue.
It would be the best to find how to prevent the exception but for the time being we might log it just as a warning instead (will go to the log but will not be shown to the end user)