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.
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.
This is a good suggestion, we have been thinking about this as well - thanks for providing real-life usecase Gili.
Changing the summary to describe the feature in a more general way
Assigning Misha as the owner, as he is the only one that can implement this
Suggesting to postpone after 1.0
Milestone cleanup: future->next