breautek commented on issue #740: URL: https://github.com/apache/cordova-android/issues/740#issuecomment-3667657776
I've done some reading on this and I don't believe this is an issue. The double-checked issue is mostly involved when publishing new objects. So if there is a local variable that is checked, followed by a synchronized block, followed by another check. If a thread instantiated a new object and assigned that object to that variable, that object may not be visible to all threads leading to crashes. This is a problem with how java manages memory and they added a volatile keyword to work around this problem. The code in question does not appear to be instantiating new objects. So the double check lock vulnerability doesn't apply. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
