Tue, 18 Jun 2013 12:31:07 -0700 8015237: Parallelize string table scanning during strong root processing
johnc [Tue, 18 Jun 2013 12:31:07 -0700] rev 18091
8015237: Parallelize string table scanning during strong root processing Summary: Parallelize the scanning of the intern string table by having each GC worker claim a given number of buckets. Changes were also reviewed by Per Liden <per.liden@oracle.com>. Reviewed-by: tschatzl, stefank, twisti
Fri, 14 Jun 2013 08:02:32 +0200 8012265: VM often crashes on solaris with a lot of memory
brutisso [Fri, 14 Jun 2013 08:02:32 +0200] rev 18090
8012265: VM often crashes on solaris with a lot of memory Summary: Increase HeapBaseMinAddress for G1 from 256m to 1g on Solaris x86 Reviewed-by: mgerdin, coleenp, kvn
Wed, 19 Jun 2013 18:13:52 +0200 Merge
nloodin [Wed, 19 Jun 2013 18:13:52 +0200] rev 18089
Merge
Tue, 18 Jun 2013 09:08:35 -0700 8015660: Test8009761.java "Failed: init recursive calls: 24. After deopt 25"
minqi [Tue, 18 Jun 2013 09:08:35 -0700] rev 18088
8015660: Test8009761.java "Failed: init recursive calls: 24. After deopt 25" Summary: Windows reserves and only partially commits thread stack. For detecting more thread stack space for execution, Windows installs one-shot page as guard page just before the current commited edge. It will trigger STACK_OVERFLOW_EXCEPTION when lands on last 4 pages of thread stack space. StackYellowPages default value is 2 on Windows (plus 1 page of StackRedPages, 3 pages guarded by hotspot) so the exception happens one page before Yellow pages. Same route executed second time will have one more page brought in, this leads same execution with different stack depth(interpreter mode). We need match Windows settings so the stack overflow exception will not happen before Yellow pages. Reviewed-by: dholmes Contributed-by: andreas.schoesser@sap.com
(0) -10000 -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip