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: | freeze when "Go to Source" | ||
|---|---|---|---|
| Product: | javaee | Reporter: | Marian Petras <mpetras> |
| Component: | JSP Parser | Assignee: | Petr Hejl <phejl> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | Keywords: | THREAD |
| Priority: | P3 | ||
| Version: | 7.1.1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | thread-dump | ||
I do not see any explicit deadlock. Is this still reproducible? I did not report a deadlock. I reported a freeze. From the thread-dump, it rather looks like a starvation - a thread invokes wait() but no other thread awakes it so the thread keeps waiting forever. Because the waiting thread was "AWT-EventQueue-1", the IDE stopped processing UI events. Regarding the question about reproducibility: It is difficult to reproduce issues caused by bad locking and/or synchronization. I can only say that I have not seen the bug since the day I reported it. |
Created attachment 118998 [details] thread-dump Just after startup, I had several JSP files open. In one of them, I Ctrl-clicked on a reference to another JSP file. After a while, dialogue "Lengty operation in progress" appeared, with text "Go to Source" (scanning of projects was not finished yet). The progress of the Scanning projects task stopped, i.e. the task did not continue (0% CPU usage) and the dialogue "Lengthy operation..." never disappeared. I tried to cancel the operation by clicking the Cancel button in the dialogue but NetBeans did not react. After a while, I used JVisualVM to generate a thread-dump - see the attachment. -- NetBeans 7.1.1 Windows 7 64-bit JDK 6u32 64-bit quad-core Intel CPU