summaryrefslogtreecommitdiffstats
path: root/make/newtversion-cdc
diff options
context:
space:
mode:
authorSven Gothel <[email protected]>2014-09-23 03:56:04 +0200
committerSven Gothel <[email protected]>2014-09-23 03:57:05 +0200
commit8e9407ab74f672c2a0d1e196a3ba2e7d8743debf (patch)
tree827d4f0dd8973ec19d31338b239eb52a6352cf04 /make/newtversion-cdc
parent2fc3a60ed01501727f0645f35ffe75eb56a32aec (diff)
Fix synchronization issues in Animator* Exception casev2.2.2
Refines commit cef7ba607ad7e8eb1ff2a438d77710a29aa0bda6 - The animator monitor-lock was still hold in the post finally block issuing flushGLRunnables(), due to intrinsic monitor release (in finally): - <http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-2.html#jvms-2.11.10> - <http://stackoverflow.com/questions/10743285/behavior-of-a-synchronized-method-with-try-and-finally> - Further: AnimatorBase.flushGLRunnables() acquired the lock itself (duh!) This commit removes the requirement for finally altogether by simply return a boolean from handleUncaughtException(caughtException), where false denotes the caller to propagate the exception itself (no handler). Post synchronized block then issues flushGLRunnables() and exceptation propagation as required. AnimatorBase.flushGLRunnables() 'synchronized' modifier is removed. Further, ThreadDeath is being propagated if caught. Here the finally block is also removed - redundant.
Diffstat (limited to 'make/newtversion-cdc')
0 files changed, 0 insertions, 0 deletions