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 50671 - Enhance Thread display with info on where in code (stack trace) it was created
Summary: Enhance Thread display with info on where in code (stack trace) it was created
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-20 17:55 UTC by _ gtzabari
Modified: 2009-05-25 21:03 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ gtzabari 2004-10-20 17:55:53 UTC
I don't know if JFluid does this yet or not (I've
yet to use it) but please add this support if you
haven't already:

Often I'm trying to figure out why my application
won't shut down once the last GUI window is
closed. Often this is the result of some thread
being spawn but not stopped or if I forget to call
dispose() on some component. Often I can locate
which Thread is responsible, but I have no idea
who spawn it (hence whose component should be
disposed).

Could you please add functionality that allows one
to track thread creation back to a stack-trace
(i.e. who created it, give a stack-trace for that
point of execution) and based upon that we should
be able to track who created *that* component and
so on... Eventually this will lead back to the
application code and we will be able to figure out
which component needed to be shut down but we did
not do it.
Comment 1 iformanek 2004-10-20 18:07:44 UTC
This is a good suggestion, we have been thinking about this as well -
thanks for providing real-life usecase Gili.
Comment 2 iformanek 2005-02-14 12:59:45 UTC
Changing the summary to describe the feature in a more general way
Comment 3 iformanek 2005-03-29 14:45:59 UTC
Assigning Misha as the owner, as he is the only one that can implement this
Comment 4 iformanek 2005-04-14 15:08:00 UTC
Suggesting to postpone after 1.0
Comment 5 Tomas Hurka 2009-04-08 12:56:43 UTC
Milestone cleanup: future->next