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.
I was editing a JUnit 4.5 test case. It removed (expected=NullPointerException.class) as a selected block from an @Test annotation. I then selected and tried to change some text within that method and got this exception. I should note that I had not long ago renamed the JUnit test class.
Created attachment 82182 [details] thread dump retrieved using the Visual VM 1.1.1
Product Version: NetBeans IDE Dev (Build 200905141401) Java: 1.6.0_11; Java HotSpot(TM) Client VM 11.0-b16 System: Windows XP version 5.1 running on x86; Cp1252; en_GB (nb)
*** Issue 165268 has been marked as a duplicate of this issue. ***
I assume this can't be reliably reproduced. It looks like the assert statements in CRR.setCurrenTask somehow slipped through Tomas' fingers when he was unifying the threading model. And now after fixing issue #164258 (http://hg.netbeans.org/jet-main/rev/823cff42a0da) there are two different locks (CRR_LOCK and INTERNAL_LOCK) being locked in opposite order. Anyway, IMO the fix is simple and I'm going to attach a patch. Tomasi please review and possibly apply. Thanks
Created attachment 82228 [details] No code synchronizes on Source anymore
Fixed jet-main 92ac77d0dafd
Integrated into 'main-golden', will be available in build *200905190201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/92ac77d0dafd User: Tomas Zezula <tzezula@netbeans.org> Log: #165262:[67cat] Deadlock between SourceCache and CurrentRequestReference
*** Issue 165492 has been marked as a duplicate of this issue. ***
*** Issue 165518 has been marked as a duplicate of this issue. ***
*** Issue 165515 has been marked as a duplicate of this issue. ***
*** Issue 165438 has been marked as a duplicate of this issue. ***
*** Issue 166052 has been marked as a duplicate of this issue. ***