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.
Product Version: NetBeans IDE Dev (Build 200711070000) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) Steps to reproduce: - Start CPU profiling of Anagram Game application - Open VM Telemetry [Overview], Threads / Loaded Classes Graph - Open Threads, enable monitoring of threads - RESULT: Threads window shows 10 live threads, VM Telemtry 8 threads
changing milestone
Confirmed it's a bug, org.netbeans.lib.profiler.server.Monitors.getMonitoredNumbers() computes wrong nTotalThreads, nSystemThreads and nUserThreads and the chart incorrectly displays nSystemThreads + nUserThreads (computed in org.netbeans.lib.profiler.results.monitor.VMTelemetryDataManager.addValuesInternal()).
Fixed in profiler-main changeset: 241504:70d05c53d451 user: Tomas Hurka <thurka@netbeans.org> date: Wed Dec 05 20:47:29 2012 +0100 summary: bugfix #121381, set nSystemThreads to 0 if the number of system threads is not known; use ThreadInfo.getLiveServerThreads() to find out number of profiler (server) internal threads
Integrated into 'main-golden', will be available in build *201212070001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/70d05c53d451 User: Tomas Hurka <thurka@netbeans.org> Log: bugfix #121381, set nSystemThreads to 0 if the number of system threads is not known; use ThreadInfo.getLiveServerThreads() to find out number of profiler (server) internal threads