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 55517 - java.lang.Thread objects references being held by profiler? Doesn't get garbage collected
Summary: java.lang.Thread objects references being held by profiler? Doesn't get garba...
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: mishadmitriev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-25 04:39 UTC by jchristi
Modified: 2007-02-20 18:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ThreadTestt.java source code (1.41 KB, text/plain)
2005-02-25 04:47 UTC, jchristi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jchristi 2005-02-25 04:39:24 UTC
I will attach source code to class "ThreadTest".

Creates 50 threads which then eventually die.

While you do memory profiling, you can see the JVM
thread count drop as they die via the JVM
telemetry, but the profiling results shows 50 live
allocated object even after all the threads have
terminated.

When I saw this happen, I had memory profiling via
connect at startup with the following settings:
record the entire object lifecycle and get full
depth, every 1 allocation, run garbage collection
with each get results.
Comment 1 jchristi 2005-02-25 04:47:19 UTC
Created attachment 20509 [details]
ThreadTestt.java source code
Comment 2 mishadmitriev 2005-02-25 22:37:33 UTC
Self assign
Comment 3 mishadmitriev 2005-02-27 08:38:02 UTC
Fixed in M6
Comment 4 ehucka 2006-10-09 12:11:41 UTC
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-12 22:53:44 UTC
Closing old issues.
Comment 6 Alexander Kouznetsov 2007-02-20 18:19:06 UTC
Reverting to the original Target Milestone value changed by mistake. Sorry for
inconvenience.