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 262338 - Apparent deadlock on startup
Summary: Apparent deadlock on startup
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 8.1
Hardware: Macintosh (x86) Mac OS X
: P3 normal (vote)
Assignee: Antonin Nebuzelsky
Depends on:
Reported: 2016-06-05 13:14 UTC by andrewgilmartin
Modified: 2016-06-06 12:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Jstack dump/log (18.21 KB, application/octet-stream)
2016-06-05 13:14 UTC, andrewgilmartin
messages.log (50.75 KB, application/octet-stream)
2016-06-05 13:15 UTC, andrewgilmartin

Note You need to log in before you can comment on or make changes to this bug.
Description andrewgilmartin 2016-06-05 13:14:47 UTC
Created attachment 159964 [details]
Jstack dump/log

When starting NB it hangs forever. Deleting /Users/ajg/Library/Application Support/NetBeans/8.1 will allow me to start NB. I have not been able to track down to which setting is causing the issue. However, the stack trace does show 2 subversion threads waiting on the same object. JConsole deadlock detection says there is none, but this looks like deadlock to my eyes. Attached are my stack trace and messages.log.
Comment 1 andrewgilmartin 2016-06-05 13:15:08 UTC
Created attachment 159965 [details]
Comment 2 Ondrej Vrabec 2016-06-05 15:48:08 UTC
I don't see any deadlock, not even in subversion threads. The fact that two threads are waiting for the same lock does not mean there is a deadlock.
AWT is in RUNNABLE state:
"AWT-EventQueue-0" #20 prio=6 os_prio=31 tid=0x00007fb241a22800 nid=0xd107 runnable [0x000000012ef4c000]
   java.lang.Thread.State: RUNNABLE
	at Method)

Maybe an issue with JDK on MacOS
Comment 3 andrewgilmartin 2016-06-06 12:50:18 UTC
Yes, the beach ball was spinning, but otherwise the UI was unresponsive. As to OS X, there may well be a problem there. After one such incident I upgrade from jdk 1.8.0_66 to 1.8.0_92 and NB strated without issue. But that only relieved the issue for less than a day.