- 26 7月, 2013 1 次提交
-
-
由 darcy 提交于
Reviewed-by: lancea, mduigou, alanb
-
- 08 7月, 2013 1 次提交
-
-
由 mchung 提交于
Summary: When enqueuing references check whether the j.l.r.Reference has already been enqeued or removed in the lock. Do not enqueue them again. This occurs because multiple threads may try to enqueue the same j.l.r.Reference at the same time. Reviewed-by: mchung, dholmes, plevart, shade Contributed-by: thomas.schatzl@oracle.com
-
- 27 5月, 2013 1 次提交
-
-
由 plevart 提交于
Summary: Catch OutOfMemoryError in reference handler thread if caused by allocation of an InterruptedException Reviewed-by: dholmes, alanb
-
- 02 11月, 2012 1 次提交
-
-
由 alanb 提交于
Reviewed-by: chegar, ksrini
-
- 01 11月, 2011 1 次提交
-
-
由 ysr 提交于
4268317: (ref) Reference.isEnqueued() can return true when instance not enqueued Summary: The reference handler now declares, and assumes, that the discovered field, rather than the next field, is (to be) used to link the entries in the pending list, thus allowing a reference object to be safely enqueued even while it is in the pending state. Also added slightly modified regression tests from the two bug reports. Reviewed-by: mchung, alanb, jcoomes
-
- 26 5月, 2010 1 次提交
-
-
由 ohair 提交于
Reviewed-by: darcy, weijun
-
- 01 12月, 2007 1 次提交
-
-
由 duke 提交于
-