Page History

According to the Java API \[[API 2006|AA. JavaBibliography#API References#API 06]\], {{BufferedReader.readLine()}} method documentation:

In a server-class machine using a parallel garbage collector, the default initial and maximum heap sizes are as follows for J2SE 6.0 \[[Sun 2006|AA. JavaBibliography#Sun References#Sun 06]\]:

The {{OutOfMemoryError}} can be avoided by ensuring that there are no infinite loops or memory leaks and no unnecessary object retention. If memory requirements are known ahead of time, the heap size can be tailored to fit the requirements using the following runtime parameters \[[Java 2006|AA. Java References#JavaBibliography#Java 06]\]:

According to the Java API \[[API 2006|AA. Java References#APIBibliography#API 06]\], Class {{ObjectInputStream}} documentation:

\[[Sun 2006|AA. Java References#SunBibliography#Sun 06]\] [Garbage Collection Ergonomics|http://java.sun.com/javase/6/docs/technotes/guides/vm/gc-ergonomics.html ], "Default values for the Initial and Maximum heap size"
\[[Java 2006|AA. JavaBibliography#Java References#Java 06]\] [java - the Java application launcher|http://java.sun.com/javase/6/docs/technotes/tools/windows/java.html ], "Syntax for increasing the heap size"
\[[Sun 2003|AA. JavaBibliography#Sun References#Sun 03]\] Chapter 5: Tuning the Java Runtime System, [Tuning the Java Heap|http://docs.sun.com/source/817-2180-10/pt_chap5.html#wp57027] 
\[[API 2006|AA. Java References#APIBibliography#API 06]\] Class ObjectInputStream and ObjectOutputStream
\[[SDN 2008|AA. Java References#SDNBibliography#SDN 08]\] [Serialization FAQ|http://java.sun.com/javase/technologies/core/basic/serializationFAQ.jsp] 
\[[MITRE 2009|AA. Java References#MITREBibliography#MITRE 09]\] [CWE-400|http://cwe.mitre.org/data/definitions/400.html] "Uncontrolled Resource Consumption (aka 'Resource Exhaustion')," [CWE-770|http://cwe.mitre.org/data/definitions/770.html], "Allocation of Resources Without Limits or Throttling"