This week's book giveaway is in the Design forum.
We're giving away four copies of Building Microservices and have Sam Newman on-line!
See this thread for details.
The moose likes Performance and the fly likes OutofMemoryError - Memory:RAM size Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Building Microservices this week in the Design forum!
JavaRanch » Java Forums » Java » Performance
Bookmark "OutofMemoryError - Memory:RAM size" Watch "OutofMemoryError - Memory:RAM size" New topic

OutofMemoryError - Memory:RAM size

kri shan
Ranch Hand

Joined: Apr 08, 2004
Posts: 1396
What is the ratio of Memory(RAM) to heap space ? ie: When JVM will throw OutOfMemoryError based on heap available to JVM ?
Ninad Naik

Joined: Jun 11, 2012
Posts: 4

JVM will throw OutOfMemoryError when:
-A new object is to be created
-JVM heap memory(defined by -Xmx) is full
-A full garbage collection isn't able to free enough space to be allocated to the new object.

Not sure what "ratio" you're talking about.
Muhammad Khojaye
Ranch Hand

Joined: Apr 12, 2009
Posts: 449

This is from JDK Doc,

The concurrent collector will throw an OutOfMemoryError if too much time is being spent in garbage collection: if more than 98% of the total time is spent in garbage collection and less than 2% of the heap is recovered, an OutOfMemoryError will be thrown. This feature is designed to prevent applications from running for an extended period of time while making little or no progress because the heap is too small. If necessary, this feature can be disabled by adding the option -XX:-UseGCOverheadLimit to the command line.

check out doc for more information.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: OutofMemoryError - Memory:RAM size
It's not a secret anymore!