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 82279 - Deadlock during memory profiling of netbeans
Summary: Deadlock during memory profiling of netbeans
Status: VERIFIED DUPLICATE of bug 84002
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2006-08-09 14:32 UTC by ehucka
Modified: 2006-10-23 16:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
profiled ide's threadsdump (28.38 KB, text/plain)
2006-08-09 14:39 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 2006-08-09 14:32:24 UTC 
I tried to reproduce issue 70287 using last trunk profiler and jdk 1.6.0.
After I invoked the last step the profiled ide got to a java deadlock.
I'll try to reproduce it again.
Comment 1 ehucka 2006-08-09 14:39:01 UTC 
Created attachment 32711 [details]
profiled ide's threadsdump
Comment 2 ehucka 2006-08-09 17:11:07 UTC 
I cannot reproduce it.
Comment 3 Jiri Sedlacek 2006-08-09 17:37:59 UTC 
I've experienced similar deadlock on Windows between OpenIDE-request-processor-
0 and AWT-EventQueue-1 when trying to reproduce Issue 70287 exactly following 
the steps provided there.
Comment 4 Tomas Hurka 2006-09-01 20:01:35 UTC 

*** This issue has been marked as a duplicate of 84002 ***
Comment 5 ehucka 2006-09-11 19:05:33 UTC 
verified