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.
| Summary: | Apparent deadlock on startup | ||
|---|---|---|---|
| Product: | platform | Reporter: | andrewgilmartin <andrewgilmartin> |
| Component: | -- Other -- | Assignee: | Antonin Nebuzelsky <anebuzelsky> |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 8.1 | ||
| Hardware: | Macintosh (x86) | ||
| OS: | Mac OS X | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
Jstack dump/log
messages.log |
||
Created attachment 159965 [details]
messages.log
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 com.sun.glass.ui.mac.MacApplication._runLoop(Native Method) at com.sun.glass.ui.mac.MacApplication.runLoop(MacApplication.java:83) at com.sun.glass.ui.Application.run(Application.java:153) Maybe an issue with JDK on MacOS 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. |
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.