Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via by Unknown author

    An easy way to solve OutOfMemoryError in java is to increase the maximum heap size by using JVM options -Xmx512M, this will immediately solve your OutOfMemoryError.

  2. ,
    via Stack Overflow by Eugene Yokota

    In Eclipse : go to Run --> Run Configurations --> then select the project under maven build --> then select the tab "JRE" --> then enter -Xmx1024m.

    This should increase the memory heap for all the builds/projects. The above memory size is 1 GB.

Solutions on the web

via by Unknown author, 1 year ago
( java.lang.AbstractStringBuilder.append( java.lang.StringBuffer.append( weka.classifiers.bayes.NaiveBayes.toString( weka.gui.explorer.ClassifierPanel$
via by Unknown author, 1 year ago
via Stack Overflow by joshuar
, 1 year ago
Requested array size exceeds VM limit
via Stack Overflow by Jinfeng
, 2 years ago
via by Unknown author, 2 years ago
via GitHub by donghwan-shin
, 2 years ago
GC overhead limit exceeded
java.lang.OutOfMemoryError: Requested array size exceeds VM limit    java.util.Arrays.copyOf(
    weka.gui.explorer.ClassifierPanel$	at java.util.Arrays.copyOf(	at java.lang.AbstractStringBuilder.expandCapacity(	at java.lang.AbstractStringBuilder.ensureCapacityInternal(	at java.lang.AbstractStringBuilder.append(	at java.lang.StringBuffer.append(	at weka.classifiers.bayes.NaiveBayes.toString(	at weka.gui.explorer.ClassifierPanel$