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 166100 - Deadlock after startup when exploring main menu
Summary: Deadlock after startup when exploring main menu
Status: RESOLVED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: Parsing & Indexing (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jan Jancura
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-27 12:30 UTC by Petr Jiricka
Modified: 2009-05-27 17:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (9.89 KB, text/plain)
2009-05-27 12:31 UTC, Petr Jiricka 		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 Petr Jiricka 2009-05-27 12:30:19 UTC 
After installing the IDE, but before activating any features, I was moving around in the menu, opened Window ->
Services, then deadlock happened. See the attachment.
Comment 1 Petr Jiricka 2009-05-27 12:31:45 UTC 
Created attachment 82854 [details]
Thread dump
Comment 2 David Strupl 2009-05-27 14:22:33 UTC 
Are you sure that it is a deadlock? I assume this is not about NB 5.0 right? Have you checked the thread dump before
attaching it? Build info would be nice ...
Comment 3 Petr Jiricka 2009-05-27 14:27:29 UTC 
Sorry, here it is. It is in trunk (6.8) from http://bertram.netbeans.org/hudson/job/web-main/, but I assume it could
also apply to 6.7:

  Product Version         = NetBeans IDE Dev (Build web-main-705-on-090527)
  Operating System        = Mac OS X version 10.5.7 running on x86_64
  Java; VM; Vendor        = 1.6.0_07; Java HotSpot(TM) 64-Bit Server VM 1.6.0_07-b06-57; Apple Inc.
  Runtime                 = Java(TM) SE Runtime Environment 1.6.0_07-b06-153

No I am not sure it's a deadlock, just the UI was unresponsive and the processor was idle and after several minutes I
had to kill the IDE.
Comment 4 Jan Jancura 2009-05-27 14:37:34 UTC 
There is nothing wrong on our side. TaskProcessor is waiting on a next task. 
You should file this issue to your VM provider.
Comment 5 Vitezslav Stejskal 2009-05-27 17:11:22 UTC 
Umm, the only thread that was doing something was AWT-EventQueue-1, its state was RUNNING, but it apparently got stuck
in some native code in apple.awt.CWindow._setVisible(). I'm afraid there really is not much we can do about this.