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 200708270000) Java: 1.5.0_12; Java HotSpot(TM) Client VM 1.5.0_12-b04 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) I come to this problem quite often when I perform NetBeans profiling in the following scenario: - Use NetBeans IDE Dev (Build 200708270000) (Java EE) with clean userdir, having specified JDK 1.5 and removed "-J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled" flags - Perform Calibration - Run another instance of IDE with customized clean userdir and parameters for direct attach like in the following command "C:\Program Files\NetBeans 6.0 200708270000\bin\nb.exe" --userdir C:\Work\Temp\NBHome "-J-agentpath:C:\Program Files\NetBeans 6.0 200708270000\profiler2\lib\deployed\jdk15\windows\profilerinterface.dll=C:\Program Files\NetBeans 6.0 200708270000\profiler2\lib,5140" - Perform Attach Profiler action for External Application Memory Allocation Profiling, each 100 objects, Record stack traces, Local Direct Attach to Application. - Open VM Telemetry Overview window - Invoke Take Snapshot action at different moments - RESULT: No snapshot is created and "Profiled Application doesn't respond" message is shown. After that no profiling is possible. User had to kill profiled IDE.
Created attachment 47816 [details] Profiler output 1
Created attachment 47817 [details] Profiled Application output 1
Created attachment 47818 [details] Profiler output 2
Created attachment 47819 [details] Profiled Application output 2
Thread dumps look strange. It is not clear what is going on.
Even it is random it is highly reproducible. And it is not that high reproducible with JDK 1.6 (if reproducible at all).
Created attachment 47987 [details] server thread dump
Created attachment 47988 [details] client thread dump
Fixed in trunk.
Well, I'm not sure whether it is the same issue, at least I'm not able to verify this one. When I performed the steps I got to the state when both profiler and profiled IDE became frozen. And I believe it happened in the same moment as for the original issue.
Created attachment 52141 [details] Profiler output and Thread Dump
Created attachment 52143 [details] Profiled App output and thread dump
This is different issue. This looks like problem in socket handling in JDK 5. It should work fine in JDK 6. Please file separate issue.
OK, filed new issue 120689. Until it is fixed I can't verify this one.
VERIFIED in Build 200811240201