Home | History | Annotate | Download | only in doc

Lines Matching full:synchronize

338 <tr bgcolor="#ffffff"><td><a href="#NP_SYNC_AND_NULL_CHECK_FIELD">NP: Synchronize and null check on the same field.</a></td><td>Multithreaded correctness</td></tr>
3498 <p>See CERT <a href="https://www.securecoding.cert.org/confluence/display/java/CON08-J.+Do+not+synchronize+on+objects+that+may+be+reused">CON08-J. Do not synchronize on objects that may be reused</a> for more information.</p>
3516 <p>See CERT <a href="https://www.securecoding.cert.org/confluence/display/java/CON08-J.+Do+not+synchronize+on+objects+that+may+be+reused">CON08-J. Do not synchronize on objects that may be reused</a> for more information.</p>
3533 <p>See CERT <a href="https://www.securecoding.cert.org/confluence/display/java/CON08-J.+Do+not+synchronize+on+objects+that+may+be+reused">CON08-J. Do not synchronize on objects that may be reused</a> for more information.</p>
3609 <p> A typical bug matching this bug pattern is forgetting to synchronize
3773 <h3><a name="NP_SYNC_AND_NULL_CHECK_FIELD">NP: Synchronize and null check on the same field. (NP_SYNC_AND_NULL_CHECK_FIELD)</a></h3>
3778 thrown and the check would be pointless. Better to synchronize on
3992 subclasses will synchronize on the class object for the subclass, which isn't likely what was intended.
4003 <p>Subclasses of <code>Label</code> won't synchronize on the same subclass, giving rise to a datarace.
5127 Multithread correctness is suspect. You should not synchronize nor call semaphore methods on