1. 27 10月, 2010 1 次提交
  2. 26 10月, 2010 1 次提交
    • A
      Merge · e1af249a
      acorn 提交于
      e1af249a
  3. 23 10月, 2010 1 次提交
  4. 21 10月, 2010 1 次提交
  5. 19 10月, 2010 1 次提交
    • N
      Merge · 044288ff
      never 提交于
      044288ff
  6. 16 10月, 2010 2 次提交
  7. 15 10月, 2010 2 次提交
    • J
      Merge · 16bbccbf
      jcoomes 提交于
      16bbccbf
    • K
      Merge · 78b3ada8
      kvn 提交于
      78b3ada8
  8. 14 10月, 2010 2 次提交
    • R
      Merge · 766034c2
      roland 提交于
      766034c2
    • T
      Merge · 27925402
      twisti 提交于
      27925402
  9. 13 10月, 2010 6 次提交
  10. 12 10月, 2010 2 次提交
  11. 11 10月, 2010 1 次提交
  12. 09 10月, 2010 1 次提交
    • J
      Merge · 7d9eea06
      jcoomes 提交于
      7d9eea06
  13. 08 10月, 2010 4 次提交
  14. 07 10月, 2010 2 次提交
  15. 06 10月, 2010 2 次提交
  16. 05 10月, 2010 5 次提交
  17. 02 10月, 2010 6 次提交
    • T
      Added tag hs20-b01 for changeset 5511edd5d719 · b3f0ab02
      trims 提交于
      b3f0ab02
    • C
      Added tag jdk7-b112 for changeset 5511edd5d719 · cee5486c
      cl 提交于
      cee5486c
    • T
      6980838: G1: guarantee(false) failed: thread has an unexpected active value in its SATB queue · acd6a8e3
      tonyp 提交于
      Summary: Under certain circumstances a safepoint could happen between a JavaThread object being created and that object being added to the Java threads list. This could cause the active field of that thread's SATB queue to get out-of-sync with respect to the other Java threads. The solution is to activate the SATB queue, when necessary, before adding the thread to the Java threads list, not when the JavaThread object is created. The changeset also includes a small fix to rename the surrogate locker thread from "Surrogate Locker Thread (CMS)" to "Surrogate Locker Thread (Concurrent GC)" since it's also used in G1.
      Reviewed-by: iveresov, ysr, johnc, jcoomes
      acd6a8e3
    • J
      Merge · 813d5b79
      johnc 提交于
      813d5b79
    • J
      6983311: G1: LoopTest hangs when run with -XX:+ExplicitInvokesConcurrent · 52b8d7bd
      johnc 提交于
      Summary: Clear the concurrent marking "in progress" flag while the FullGCCount_lock is held. This avoids a race that can cause back to back System.gc() calls, when ExplicitGCInvokesConcurrent is enabled, to fail to initiate a marking cycle causing the requesting thread to hang.
      Reviewed-by: tonyp, ysr
      52b8d7bd
    • Y
      6794422: Perm gen expansion policy for concurrent collectors · 9747275e
      ysr 提交于
      Summary: Concurrent collectors should expand the perm gen without a full STW GC, but possibly by triggering a concurrent collection. Temporary band-aid for G1 where no concurrent collection is kicked off since the perm gen is not collected concurrently.
      Reviewed-by: johnc
      9747275e