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 65803 - Deadlock in profiled app due to profiler
Summary: Deadlock in profiled app due to profiler
Status: CLOSED DUPLICATE of bug 65614
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-04 08:34 UTC by _ rkubacki
Modified: 2007-02-20 18:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
thread dump (28.18 KB, text/plain)
2005-10-04 08:35 UTC, _ rkubacki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2005-10-04 08:34:28 UTC
Linux, JDK1.5.0_04, profiling from NB4.1+profilerM8v3, profiled app is dev build
of NetBeans5.0

I started profiling with analyze performance using filter to exclude
java.*,javax.*,sun.*,com.*,or.w3c.* classes and it goes slowly to the point
where winsys of starting NetBeans should be restored and the profiled app
reaches deadlock state.
Comment 1 _ rkubacki 2005-10-04 08:35:06 UTC
Created attachment 25485 [details]
thread dump
Comment 2 iformanek 2005-10-10 16:00:13 UTC

*** This issue has been marked as a duplicate of 65614 ***
Comment 3 ehucka 2006-10-09 12:10:11 UTC
Verification of old issues.
Comment 4 Alexander Kouznetsov 2007-02-20 10:26:58 UTC
Closing old issues
Comment 5 Alexander Kouznetsov 2007-02-20 18:10:17 UTC
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.