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 54645 - Cannot profile the Profiler on itself
Summary: Cannot profile the Profiler on itself
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: mishadmitriev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-07 21:21 UTC by mishadmitriev
Modified: 2007-02-12 22:21 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 mishadmitriev 2005-02-07 21:21:39 UTC 
Due to certain properties of the wireprotocol 
code (static variables used in a number of places 
to somewhat simplify design and improve 
performance), it's not possible to have two 
instances of WireProtocol running correctly and 
independently inside the same JVM. Thus the 
Profiler cannot be profiled on itself. Need to 
modify the wireprotocol classes; expected loss of 
performance is likely going to be very small.
Comment 1 mishadmitriev 2005-02-07 21:22:29 UTC 
Targeted for M6
Comment 2 iformanek 2005-04-12 13:57:36 UTC 
Postponed to M7
Comment 3 iformanek 2005-05-10 14:55:43 UTC 
Done in M7
Comment 4 ehucka 2006-10-09 12:11:42 UTC 
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-12 22:21:43 UTC 
Closing old issues.