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.

Bug 65968 - A deadlock from memory profiling - getStackTrace
Summary: A deadlock from memory profiling - getStackTrace
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All Linux
: P2 blocker (vote)
Assignee: iformanek
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2005-10-05 13:53 UTC by ehucka
Modified: 2006-10-09 10:48 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
threads dump (10.20 KB, text/plain)
2005-10-05 13:54 UTC, ehucka 		Details
ide threaddump (11.01 KB, text/plain)
2005-10-05 14:25 UTC, ehucka 		Details
threaddump (9.32 KB, text/plain)
2005-11-07 16:59 UTC, ehucka 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2005-10-05 13:53:41 UTC 
build 051005, both os remote/local linux fc3, jdk1.5.0_05

I've profiled a remote application - memory profiling, object liveness
The deadlock is reproducible.
Comment 1 ehucka 2005-10-05 13:54:59 UTC 
Created attachment 25555 [details]
threads dump
Comment 2 ehucka 2005-10-05 14:25:03 UTC 
I've tried to reproduce it again and after the deadlock occured and I confirmed
dialog about finishing of profiled application IDE froze.
Comment 3 ehucka 2005-10-05 14:25:57 UTC 
Created attachment 25556 [details]
ide threaddump
Comment 4 iformanek 2005-10-17 11:28:08 UTC 
Fixed.
Comment 5 iformanek 2005-10-18 10:46:13 UTC 
Reopening, the bugfix needs to be reverted
Comment 6 iformanek 2005-10-18 16:57:13 UTC 
Should be fixed by reverting fix for issue 60323, please reopen if this occurs 
again.
Comment 7 ehucka 2005-11-07 09:49:35 UTC 
it is still there:

"*** Profiler Agent Special Execution Thread ***":
        at
com.sun.tools.profiler.server.ProfilerInterface$1.handleEventBufferDump(ProfilerInterface.java:109)
        - waiting to lock <0xed73de70> (a java.lang.Object)
        at
com.sun.tools.profiler.server.ProfilerRuntime.dumpEventBuffer(ProfilerRuntime.java:242)
        - locked <0xed74f180> (a [B)
        at
com.sun.tools.profiler.server.ProfilerInterface.dumpExistingResults(ProfilerInterface.java:332)
        at
com.sun.tools.profiler.server.ProfilerServer$SeparateCmdExecutionThread.run(ProfilerServer.java:972)
        - locked <0xed73d130> (a java.lang.Object)
"main":
        at
com.sun.tools.profiler.server.ProfilerRuntimeMemory.getAndSendCurrentStackTrace(ProfilerRuntimeMemory.java:228)
        - waiting to lock <0xed74f180> (a [B)
        - locked <0xf12a3ef0> (a java.lang.Class)
        at
com.sun.tools.profiler.server.ProfilerRuntimeObjLiveness.traceObjAlloc(ProfilerRuntimeObjLiveness.java:115)
Comment 8 iformanek 2005-11-07 16:42:04 UTC 
Adjusting the priority
Comment 9 iformanek 2005-11-07 16:49:26 UTC 
Emane, do you still have the full thread dump? The last info is not complete.
Comment 10 ehucka 2005-11-07 16:59:47 UTC 
Created attachment 26687 [details]
threaddump
Comment 11 iformanek 2005-11-07 18:23:44 UTC 
Fixed
Comment 12 ehucka 2005-11-11 14:47:31 UTC 
v