1. 11 12月, 2008 1 次提交
    • Y
      6782457: CMS: Livelock in CompactibleFreeListSpace::block_size() · d5a88d45
      ysr 提交于
      6736295: SIGSEGV in product jvm, assertion "these are the only valid states during a mark sweep" in fastdebug
      Summary: Restructured the code in the perm gen allocation retry loop so as to avoid "safepoint-blocking" on locks, in this case the Heap_lock, while holding uninitialized allocated heap storage.
      Reviewed-by: apetrusenko, iveresov, jcoomes, jmasa, poonam
      d5a88d45
  2. 04 12月, 2008 2 次提交
  3. 02 12月, 2008 1 次提交
  4. 26 11月, 2008 1 次提交
  5. 25 11月, 2008 2 次提交
  6. 22 11月, 2008 2 次提交
  7. 21 11月, 2008 2 次提交
    • Y
      6684579: SoftReference processing can be made more efficient · bf0e7f79
      ysr 提交于
      Summary: For current soft-ref clearing policies, we can decide at marking time if a soft-reference will definitely not be cleared, postponing the decision of whether it will definitely be cleared to the final reference processing phase. This can be especially beneficial in the case of concurrent collectors where the marking is usually concurrent but reference processing is usually not.
      Reviewed-by: jmasa
      bf0e7f79
    • Y
      6722113: CMS: Incorrect overflow handling during precleaning of Reference lists · fb7c8a34
      ysr 提交于
      Summary: When we encounter marking stack overflow during precleaning of Reference lists, we were using the overflow list mechanism, which can cause problems on account of mutating the mark word of the header because of conflicts with mutator accesses and updates of that field. Instead we should use the usual mechanism for overflow handling in concurrent phases, namely dirtying of the card on which the overflowed object lies. Since precleaning effectively does a form of discovered list processing, albeit with discovery enabled, we needed to adjust some code to be correct in the face of interleaved processing and discovery.
      Reviewed-by: apetrusenko, jcoomes
      fb7c8a34
  8. 19 11月, 2008 4 次提交
  9. 15 11月, 2008 1 次提交
    • I
      6770608: G1: Mutator thread can flush barrier and satb queues during safepoint · 5ee7f6f4
      iveresov 提交于
      6660573: G1: BigApps Failure : guarantee(satb_mq_set.completed_buffers_num() == 0,"invariant")
      Summary: When exiting a mutator thread is removed from the thread list before it has a chance to flush its SATB and barrier queues. If GC happens at this moment the objects that are refererred from these queues can be moved, which will case a crash. The fix is simply to flush the buffers before removing a thread from the list.
      Reviewed-by: jcoomes, tonyp
      5ee7f6f4
  10. 14 11月, 2008 1 次提交
  11. 13 11月, 2008 2 次提交
  12. 12 11月, 2008 3 次提交
  13. 08 11月, 2008 2 次提交
  14. 07 11月, 2008 2 次提交
  15. 31 10月, 2008 2 次提交
  16. 29 10月, 2008 3 次提交
  17. 23 10月, 2008 1 次提交
  18. 22 10月, 2008 1 次提交
  19. 15 10月, 2008 2 次提交
  20. 14 10月, 2008 3 次提交
  21. 11 10月, 2008 1 次提交
  22. 08 10月, 2008 1 次提交