1. 19 11月, 2011 1 次提交
  2. 22 11月, 2011 1 次提交
    • J
      7110173: GCNotifier::pushNotification publishes stale data. · 142413b4
      johnc 提交于
      Summary: GCNotifier::pushNotification() references GCMemoryManager::_last_gc_stat but is called from GCMemoryManager::gc_end() before GCMemoryManager::_last_gc_stat is set up using the values in GCMemoryManager::_current_gc_stat. As a result the GC notification code accesses unitialized or stale data. Move the notification call after GCMemoryManager::_las_gc_stat is set, but inside the same if-block.
      Reviewed-by: poonam, dholmes, fparain, mchung
      142413b4
  3. 21 11月, 2011 1 次提交
  4. 19 11月, 2011 1 次提交
  5. 17 11月, 2011 1 次提交
  6. 16 11月, 2011 1 次提交
  7. 10 11月, 2011 2 次提交
  8. 09 11月, 2011 5 次提交
  9. 08 11月, 2011 3 次提交
  10. 03 11月, 2011 1 次提交
  11. 02 11月, 2011 1 次提交
  12. 01 11月, 2011 1 次提交
  13. 31 10月, 2011 2 次提交
  14. 28 10月, 2011 4 次提交
  15. 27 10月, 2011 2 次提交
  16. 26 10月, 2011 4 次提交
  17. 25 10月, 2011 3 次提交
  18. 24 10月, 2011 4 次提交
    • T
      7090904: JSR 292: JRuby junit test crashes in PSScavengeRootsClosure::do_oop · 8ba5ff7e
      twisti 提交于
      Reviewed-by: kvn, never, jrose
      8ba5ff7e
    • J
      7096030: G1: PrintGCDetails enhancements · 15519f74
      johnc 提交于
      7102445: G1: Unnecessary Resource allocations during RSet scanning
      Summary: Add a new per-worker thread line in the PrintGCDetails output. GC Worker Other is the difference between the elapsed time for the parallel phase of the evacuation pause and the sum of the times of the sub-phases (external root scanning, mark stack scanning, RSet updating, RSet scanning, object copying, and termination) for that worker. During RSet scanning, stack allocate DirtyCardToOopClosure objects; allocating these in a resource area was causing abnormally high GC Worker Other times while the worker thread freed ResourceArea chunks.
      Reviewed-by: tonyp, jwilhelm, brutisso
      15519f74
    • N
      7103784: enable some flags by default · 6dc40394
      never 提交于
      Reviewed-by: kvn
      6dc40394
    • N
      7103380: assertion failure with -XX:+PrintNativeNMethods · 8cd715d7
      never 提交于
      Reviewed-by: kvn, iveresov
      8cd715d7
  19. 21 10月, 2011 1 次提交
    • J
      7099824: G1: we should take the pending list lock before doing the remark pause · 08630d11
      johnc 提交于
      Summary: Acquire the pending list lock in the prologue method of G1's concurrent VM_Operation and release the lock in the epilogue() method. The locking/unlocking order of the pending list lock and the Heap_lock should match that in the prologue and epilogue methods of VM_GC_Operation.
      Reviewed-by: tonyp, ysr
      08630d11
  20. 20 10月, 2011 1 次提交