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 144808 - [65cat][tools] Profiler cannot see NetBeans process itself for Attachment
Summary: [65cat][tools] Profiler cannot see NetBeans process itself for Attachment
Status: RESOLVED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-22 04:09 UTC by esmithbss
Modified: 2008-08-22 16:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2008-08-22 04:09:30 UTC
[ BUILD # : 200808201401 ]
[ JDK VERSION : 1.6.0_07 ]

In an attempt to profile the IDE for performance issues, When I
launched the Profiler for attaching to an existing Java 6 process,
the IDE cannot be found.

Assuming this could be a "Cannot see myself on purpose" issue I
attempted to launch a second NB instance.  The second instance was
terminated before startup.

So it appears that you cannot profile the IDE at this time.
Comment 1 Tomas Hurka 2008-08-22 12:23:24 UTC
You cannot profile itself. Profiling another instance works-for-me.
Comment 2 esmithbss 2008-08-22 15:23:58 UTC
It would be nice to profile another instance; however, I was unable to launch a second instance of NB 6.5 to profile the
first instance.  In multiple attempts, the second instance terminates before the Splash Screen is displayed.

Similarly, I was unable to attach using VirtualVM 1.0 in subsequent attempts.

Would these issues therefore be separate issues to submit, or are these indicative of a situation imposed by the NB Runtime.
Comment 3 Tomas Hurka 2008-08-22 16:20:58 UTC
If you want to run 2 instance of NetBeans they have to have different userdirs.