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 154091 - Two instances of ProfilingPointFactory are created instead of one
Summary: Two instances of ProfilingPointFactory are created instead of one
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Cyhelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-28 13:16 UTC by Petr Cyhelsky
Modified: 2009-02-19 22:56 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 Petr Cyhelsky 2008-11-28 13:16:19 UTC 
When profiling point is created two factories are created instead of one. Aside from unnecessary memory consumption it
may have unforeseen consequences (it is intended as singleton).
Comment 1 Petr Cyhelsky 2008-11-28 13:27:54 UTC 
fixed in profiler -main, changeset: 91c5f799d985
Comment 2 Petr Cyhelsky 2008-11-28 13:28:25 UTC 
f.
Comment 3 Petr Cyhelsky 2008-12-01 15:03:18 UTC 
Open some java file in editor -> place each kind of profiling point -> check via visualVM that only one instance of each
profilingpointfactory is present on the heap (all are subclasses of ProfilingPointFactory)
Comment 4 Quality Engineering 2008-12-01 17:04:21 UTC 
Integrated into 'main-golden', will be available in build *200812011401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/91c5f799d985
User: Petr Cyhelsky <cyhelsky@netbeans.org>
Log: Issue #154091 - eliminate unneded instances of various profiling point factories
Comment 5 Rashid Urusov 2008-12-02 13:34:39 UTC 
VERIFIED in Build 200812020201