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 51217 - Initial instrumentation not done when using Attach at startup mechanism
Summary: Initial instrumentation not done when using Attach at startup mechanism
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-05 21:59 UTC by jchristi
Modified: 2007-02-20 18:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jchristi 2004-11-05 21:59:26 UTC 
Ive succesfully configured my JVM to have the PATH
setup correctly and the java command line altered
so that it invokes the profilerinterface code.

I can then actually attach the the process at
startup, and I do get to see the VM telemetry, but
the "Get Current Results" menu item is never
active/not selectable.

This is so both with my custom memory profiling
and if I just use the plain anaylyze memory usage
as well.
Comment 1 jchristi 2004-11-06 04:46:31 UTC 
It appears that upon connection using this mechanism, nothing is
getting instrumented...
Comment 2 jchristi 2004-11-08 14:18:03 UTC 
This definately prevents the "Analyze Startup Performance" from being
a useful option.
Comment 3 mishadmitriev 2004-11-09 07:16:56 UTC 
Fixed, code will become available in Milestone 4 release.

Fixed version of M3 can be provided to the user upon request for 
testing.
Comment 4 iformanek 2004-11-09 15:00:35 UTC 
Fixed already in M3 v2
Comment 5 ehucka 2006-10-09 12:11:29 UTC 
Verification of old issues.
Comment 6 Alexander Kouznetsov 2007-02-12 22:40:11 UTC 
Closing old issues.
Comment 7 Alexander Kouznetsov 2007-02-20 18:34:05 UTC 
Reverting to the original Target Milestone value changed by mistake. Sorry for
inconvenience.