|
Page: Labels for this Space
|
David Svoboda |
May 18, 2016
|
|
Page: LCK00-J. Use private final lock objects to synchronize classes that may interact with untrusted code
|
Jon O'Donnell |
Aug 06, 2021
|
|
Page: LCK01-J. Do not synchronize on objects that may be reused
|
Svyatoslav Razmyslov |
Jun 25, 2021
|
|
Page: LCK02-J. Do not synchronize on the class object returned by getClass()
|
Michal Rozenau |
May 18, 2021
|
|
Page: LCK03-J. Do not synchronize on the intrinsic locks of high-level concurrency objects
|
Jon O'Donnell |
Mar 31, 2021
|
|
Page: LCK04-J. Do not synchronize on a collection view if the backing collection is accessible
|
Michal Rozenau |
May 18, 2021
|
|
Page: LCK05-J. Synchronize access to static fields that can be modified by untrusted code
|
Jon O'Donnell |
Aug 06, 2021
|
|
Page: LCK06-J. Do not use an instance lock to protect shared static data
|
Winfried Gerlach |
Mar 15, 2022
|
|
Page: LCK07-J. Avoid deadlock by requesting and releasing locks in the same order
|
Michal Rozenau |
May 18, 2021
|
|
Page: LCK08-J. Ensure actively held locks are released on exceptional conditions
|
David Svoboda |
Jun 16, 2021
|
|
Page: LCK09-J. Do not perform operations that can block while holding a lock
|
Jon O'Donnell |
Aug 06, 2021
|
|
Page: LCK10-J. Use a correct form of the double-checked locking idiom
|
Jon O'Donnell |
Aug 06, 2021
|
|
Page: LCK11-J. Avoid client-side locking when using classes that do not commit to their locking strategy
|
Carol J. Lallier |
Jun 20, 2015
|
|
Page: Leaking Capabilities
|
Carol J. Lallier |
Nov 29, 2011
|
|
Page: Leaking Sensitive Data
|
Robert Seacord (Manager) |
Apr 27, 2015
|
|
Page: Libraries
|
Shannon Haas |
Aug 03, 2011
|
