Community
Participate
Working Groups
Cloned from: 353303: RWOLockManager.unlock(CONTEXT) gives ConcurrentModEx https://bugs.eclipse.org/bugs/show_bug.cgi?id=353303 Unlocking all locks for a given context, i.e. calling RWOLockManager.unlock(CONTEXT context), causes ConcurrendModEx, due to the removal of lockStates while the set of lockStates for a given context is being iterated over. (The actual removal happens in #removeLockFromContext.) No test case was ever written for this scenario. Not sure if the old RWLockManager did it right. Doesn't matter now, will provide a fix + testcase for the RWOLockManager momentarily.
Fixed as part of bug 353691.
Sorry - not fixed in 4.0 yet!
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems. Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Moving all open bugzillas to 4.5.
Moving all unaddressed bugzillas to 4.6.
Moving all open bugs to 4.7
Moving all unresolved issues to version 4.8-
Moving all unresolved issues to version 4.9
Moving to 4.13.