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.
Created attachment 154010 [details] Profiled NetBeans IDE Steps: External attach to another NetBeans instance, all allocations of java.lang.String, expanded Java2Demo sources in Projects window and tried to open a source file. See attached thread dumps from profiled and profiling NetBeans.
Created attachment 154012 [details] Profiling NetBeans IDE
This is not always reproducible.
"Thread-8" (handleServerCommand thread) tries to obtain ProfilingSessionStatus transaction. ProfilingSessionStatus transaction is held by "pool-2-thread-1" in MemoryResultsSnapshot.<init>. "pool-2-thread-1" waits for AllocatedObjectsCountResults, but this response from TA cannot be processed, since "Thread-8" (handleServerCommand thread) is blocked.
Fixed in profiler-main changeset: 287904:28c30eb9ba0e user: Tomas Hurka <thurka@netbeans.org> date: Tue Jun 02 13:52:55 2015 +0200 summary: bugfix #252745, use instrumentation filter as early as possible; use correct class name for array classes The above fix significantly lowers the chance that this deadlock happened again. The proper fix should be probably done in MemoryResultsSnapshot to avoid calling ProfilerClient.getAllocatedObjectsCountResults() under ProfilingSessionStatus transaction.
Integrated into 'main-silver', will be available in build *201506030001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/28c30eb9ba0e User: Tomas Hurka <thurka@netbeans.org> Log: bugfix #252745, use instrumentation filter as early as possible; use correct class name for array classes