1. 26 1月, 2012 1 次提交
  2. 25 1月, 2012 1 次提交
  3. 09 1月, 2012 1 次提交
  4. 06 1月, 2012 1 次提交
  5. 05 1月, 2012 1 次提交
  6. 20 12月, 2011 1 次提交
  7. 14 12月, 2011 1 次提交
  8. 17 11月, 2011 1 次提交
  9. 14 10月, 2011 1 次提交
  10. 24 9月, 2011 1 次提交
  11. 21 9月, 2011 1 次提交
  12. 12 8月, 2011 1 次提交
  13. 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
  14. 13 5月, 2011 1 次提交
  15. 07 5月, 2011 1 次提交
  16. 22 4月, 2011 1 次提交
  17. 06 4月, 2011 1 次提交
  18. 22 3月, 2011 1 次提交
  19. 21 2月, 2011 1 次提交
  20. 11 2月, 2011 1 次提交
  21. 04 2月, 2011 1 次提交
    • B
      7015169: GC Cause not always set · 5a6ed888
      brutisso 提交于
      Summary: Sometimes the gc cause was not always set. This caused JStat to print the wrong information.
      Reviewed-by: tonyp, ysr
      Contributed-by: suenaga.yasumasa@oss.ntt.co.jp
      5a6ed888
  22. 03 2月, 2011 1 次提交
  23. 28 1月, 2011 1 次提交
  24. 15 1月, 2011 1 次提交
  25. 07 1月, 2011 1 次提交
  26. 24 11月, 2010 1 次提交
  27. 11 9月, 2010 1 次提交
  28. 28 8月, 2010 1 次提交
  29. 25 8月, 2010 1 次提交
    • T
      6941275: G1: The MemoryPools are incorrectly supported for G1 · 0807c46f
      tonyp 提交于
      Summary: The way we were caluclating the max value meant that it might fluctuate during the run and this broke some assumptions inside the MBeans framework. This change sets the max value of each pool to -1, which means undefined according to the spec.
      Reviewed-by: mchung, johnc
      0807c46f
  30. 31 7月, 2010 1 次提交
  31. 28 5月, 2010 1 次提交
  32. 23 4月, 2010 1 次提交
  33. 24 3月, 2010 1 次提交
  34. 17 3月, 2010 1 次提交
  35. 10 2月, 2010 1 次提交
  36. 07 1月, 2010 1 次提交
  37. 05 1月, 2010 1 次提交
    • Y
      6637203: Classunloading messages go to stdout rather than Xloggc file, causing... · 0698402e
      ysr 提交于
      6637203: Classunloading messages go to stdout rather than Xloggc file, causing hangs when stdout is closed
      Summary: Decoupled TraceClassUnloading from verbose:gc, JVMTI_VERBOSE_GC and PrintGC[Details], making it settable in a manner identical to TraceClassLoading. Reverted an inadvertent change of TraceClassUnloading output in a previous changeset from gclog back to tty.
      Reviewed-by: coleenp, dholmes, jmasa, poonam
      0698402e
  38. 24 12月, 2009 1 次提交
    • Y
      6631166: CMS: better heuristics when combatting fragmentation · c290220e
      ysr 提交于
      Summary: Autonomic per-worker free block cache sizing, tunable coalition policies, fixes to per-size block statistics, retuned gain and bandwidth of some feedback loop filters to allow quicker reactivity to abrupt changes in ambient demand, and other heuristics to reduce fragmentation of the CMS old gen. Also tightened some assertions, including those related to locking.
      Reviewed-by: jmasa
      c290220e
  39. 08 12月, 2009 1 次提交
  40. 04 12月, 2009 1 次提交