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: | Netbeans freezes | ||
|---|---|---|---|
| Product: | javaee | Reporter: | frankioski <frankioski> |
| Component: | JSP | Assignee: | Marek Fukala <mfukala> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | mmetelka, msauer, mslama, pribyl |
| Priority: | P3 | Keywords: | RANDOM, THREAD |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
Screen cap of IDE
Screen cap of Windows Task Manager Thread dump Frozen again. 2nd thread dump attached. NetBeans froze again! Attaching thread dump. |
||
|
Description
frankioski
2008-07-10 18:27:32 UTC
Created attachment 64268 [details]
Screen cap of IDE
Created attachment 64269 [details]
Screen cap of Windows Task Manager
Created attachment 64270 [details]
Thread dump
Created attachment 64396 [details]
Frozen again. 2nd thread dump attached.
Reassigning to "java". Seems more like debugger issue to me. Please reassign back in case I'm mistaken, thanks. I have made a fix preventing Finish Debugger action to be still enabled and non-functional: changeset d9e81876bce9 in main details: http://hg.netbeans.org/main?cmd=changeset;node=d9e81876bce9 The second thread dump does not seem to be related to the debugger. AWT thread is blocked at org.openide.text.CloneableEditor$DoInitialize.initDocument(CloneableEditor.java:352) which is called by org.netbeans.modules.java.hints.infrastructure.HintAction.getCurrentFile(HintAction.java:100) Reassigning back for further evaluation. Integrated into 'main-golden', available in build *200807310201* on http://bits.netbeans.org/dev/nightly/ Changeset: http://hg.netbeans.org/main/rev/d9e81876bce9 User: Daniel Prusa <dprusa@netbeans.org> Log: #139636: clear finishing flag on finish() method exit Created attachment 67923 [details]
NetBeans froze again! Attaching thread dump.
Last dump is from gsf, isn't it? Moving from ruby/GSF to editor/CSL. Step one: assign to myself ;-) Step 2: trying to make the owner not myself but the owner of the subcomponent. Is this still relevant? Not sure. From the threaddump it looks like a clash between AWT and "GSF Source Worker Thread". AWT: BaseKit.DefaultKeyTypedAction calls insertString under a document writelock; JSPKit$JspDefaultKeyTypedAction.insertString calls reformat which tries to acquire the GSF parsing infrastructure's lock. GSF: A task is running which tries to readlock a document. Any chance this has been resolved? I am little confused from the latest comments. Issue has INCOMPLETE status - are we really waiting for additional info from the reporter? Thanks for any update It would be nice if the reporter will tell us if it still happen for him in latest trunk builds... Thanks. Marek, these are yours now ... Last deadlock is probably due to incorrect order of locking of document and internal old gsf parser lock. mfukala do you remember if you already fixed this in past or not? Document locking in AWT thread is done at org.netbeans.editor.BaseKit$DefaultKeyTypedAction.actionPerformed. This is IMHO already fixed by my changes in JspKit$JspDefaultKeyTypedAction - the indent lock is acquired before locking the document. closing as fixed |