- 04 7月, 2013 1 次提交
-
-
由 coleenp 提交于
Summary: Return the appropriate JNI error message (instead of the generic one) when the JVM is already started Reviewed-by: coleenp, hseigel Contributed-by: sylvestre@debian.org
-
- 02 7月, 2013 3 次提交
-
-
由 coleenp 提交于
-
由 coleenp 提交于
8015391: NPG: With -XX:+UseCompressedKlassPointers OOME due to exhausted metadata space could occur when metaspace is almost empty Summary: Allocate medium chunks for class metaspace when class loader has lots of classes Reviewed-by: mgerdin, jmasa
-
由 sspitsyn 提交于
Summary: The fix is basically a backport of JDK-7019165 (pstack issue) to jhelper.d. Reviewed-by: coleenp, sspitsyn Contributed-by: tomas.hurka@oracle.com
-
- 26 6月, 2013 1 次提交
-
-
由 egahlin 提交于
Reviewed-by: stefank, brutisso, mgronlun
-
- 20 6月, 2013 3 次提交
- 19 6月, 2013 1 次提交
-
-
由 minqi 提交于
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
-
- 18 6月, 2013 3 次提交
- 12 6月, 2013 1 次提交
-
-
由 rbackman 提交于
Reviewed-by: dholmes, sla
-
- 01 7月, 2013 1 次提交
-
-
由 fparain 提交于
Reviewed-by: zgu, coleenp Contributed-by: volker.simonis@gmail.com
-
- 30 6月, 2013 2 次提交
- 28 6月, 2013 7 次提交
- 27 6月, 2013 2 次提交
- 26 6月, 2013 8 次提交
-
-
由 ehelin 提交于
Reviewed-by: jmasa, mgerdin
-
由 kevinw 提交于
-
由 kevinw 提交于
Reviewed-by: sla, dsamersoff
-
由 jmasa 提交于
Reviewed-by: tschatzl, brutisso
-
由 zgu 提交于
-
由 zgu 提交于
Summary: Fixed possible NULL pointer that caused SIGSEGV Reviewed-by: coleenp, acorn, ctornqvi
-
由 amurillo 提交于
-
由 jmasa 提交于
Reviewed-by: johnc, tschatzl
-
- 25 6月, 2013 3 次提交
- 24 6月, 2013 1 次提交
-
-
由 goetz 提交于
Summary: Replace _indy by _jsr292 and also fix VERIFY_OOP macros. Reviewed-by: kvn
-
- 26 6月, 2013 2 次提交
- 25 6月, 2013 1 次提交
-
-
由 twisti 提交于
-