JDK-8044054 : nsk/jvmti/Allocate/alloc001 OOMs again
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 6,6u101,8u20,9
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2014-05-27
  • Updated: 2015-05-14
  • Resolved: 2014-09-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Related Reports
Relates :  
RULE nsk/jvmti/Allocate/alloc001 Crash Out of Memory Error ...os_linux_x86.cpp...

# There is insufficient memory for the Java Runtime Environment to continue.
# pthread_getattr_np
# Possible reasons:
#   The system is out of physical RAM or swap space
#   In 32 bit mode, the process size limit was hit
# Possible solutions:
#   Reduce memory load on the system
#   Increase physical memory or swap space
#   Check if swap backing store is full
#   Use 64 bit Java on a 64 bit OS
#   Decrease Java heap size (-Xmx/-Xms)
#   Decrease number of Java threads
#   Decrease Java thread stack sizes (-Xss)
#   Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#  Out of Memory Error (/opt/jprt/T/P1/205835.cphillim/s/src/os_cpu/linux_x86/vm/os_linux_x86.cpp:729), pid=9791, tid=139720595007232
# JRE version: Java(TM) SE Runtime Environment (9.0-b14) (build 1.9.0-ea-fastdebug-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.9.0-internal-201405232058.cphillim.rt-8043925-fastdebug mixed mode, sharing linux-amd64 compressed oops)
Same test times out on mac.

On linux this bug can be fixed by setting the environment variable "export MALLOC_ARENA_MAX=4". MALLOC_ARENA_MAX does not solve the problem for the linked bug on mac. This test always times out on mac. I would like to solve both bugs before I submit this fix.

When virtual memory has been limited with "ulimit -v" and using GC " -XX:+UseConcMarkSweepGC", then the jvm crashes at startup. The solution is to add another GC argument to limit the GC memory use, but I have not yet found the correct GC argument to add.