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: |
Deadlock closing a file - misterious deadlock in AWT? |
| Product: |
platform
|
Reporter: |
emcmanus <emcmanus> |
| Component: |
Nodes | Assignee: |
Jaroslav Tulach <jtulach> |
| Status: |
RESOLVED
DUPLICATE
|
|
|
| Severity: |
normal
|
CC: |
issues
|
| Priority: |
P2
|
|
|
| Version: |
7.2 | |
|
| Hardware: |
Macintosh (x86) | |
|
| OS: |
Mac OS X | |
|
|
Issue Type:
|
DEFECT
|
Exception Reporter:
|
|
|---|
| Attachments: |
jstack output for deadlocked NetBeans
|
Created attachment 123566 [details] jstack output for deadlocked NetBeans I had just restarted my MacBook Pro, running Mountain Lion. I had had to restart it by power cycling because of a problem unrelated to NetBeans. Mountain Lion remembers what apps were running when it stopped so the NetBeans icon appeared in the cmd-tab list. I selected it, which caused NetBeans to launch for real, with several projects open that had been open when it crashed, and in particular two Java source files from two different projects. I clicked on the tab-close X in order to close one of those files and got the attached deadlock. I strongly doubt that it is related to the particular circumstances of the reboot, but it could be something that only happens when NetBeans is restarted after being stopped abruptly.