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.
Threads monitor UI in IDE shows states: RSSSSSSSSSWWWW But automated tests returns: RSSSSZZZZZWRWW The main thread of the application starts another thread and it is joined to the started thread.
I've tested it manualy on windows and it is probably visible (zombie states) by ui on Threads view. A thread's state bar contains sometimes white gaps.
Created attachment 27394 [details] screenshot
Is this windows only? What is the profiled application?
I cannot reproduce this on Windows with Tomcat, please be more specific about the steps to reproduce.
To reproduce: 1. create web sample project 2. invoke profile main project - cpu, entire, profile server code 3. open threads states view I cannot reproduce it manualy if I set only the Monitor application task.
Emane, it would be much much better if I had this type of information as part of the bug report. Having to go again through the same tedious process of trying to figure out the combination of things that lead to the issue just makes us inefficient. Do you know if this happens only for CPU profiling, only on Tomcat and only if Entire App server is selected?
I've omitted that automated tests call ProfilerClient.initiateRecursiveCPUProfInstrumentation(...). I have reproduced it with both Web Application and GUI application by cpu and memory profiling. I couldn't reproduce it by code region profiling. I found another strange behaviour. Some threads (suspect these with gaps) are shown 'multiple' (AWT-Event-Queue or main) see screenshot.
Created attachment 27453 [details] screenshot2
Fixed in M12, apparently, the Threads view only worked in monitoring mode, starting with M10.
verified