Exception in thread "main" java.lang.OutOfMemoryError: Java heap space not fixed

Question

this is not a duplicate question, i see this, i want to run a java prograrm and have this error:

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
    at edu.stanford.nlp.ie.crf.CRFLogConditionalObjectiveFunction.empty2D(CRFLogConditionalObjectiveFunction.java:892)
    at edu.stanford.nlp.ie.crf.CRFLogConditionalObjectiveFunction.<init>(CRFLogConditionalObjectiveFunction.java:134)
    at edu.stanford.nlp.ie.crf.CRFLogConditionalObjectiveFunction.<init>(CRFLogConditionalObjectiveFunction.java:117)
    at edu.stanford.nlp.ie.crf.CRFClassifier.getObjectiveFunction(CRFClassifier.java:1792)
    at edu.stanford.nlp.ie.crf.CRFClassifier.trainWeights(CRFClassifier.java:1798)
    at edu.stanford.nlp.ie.crf.CRFClassifier.train(CRFClassifier.java:1713)
    at edu.stanford.nlp.ie.AbstractSequenceClassifier.train(AbstractSequenceClassifier.java:763)
    at edu.stanford.nlp.ie.AbstractSequenceClassifier.train(AbstractSequenceClassifier.java:751)
    at edu.stanford.nlp.ie.crf.CRFClassifier.main(CRFClassifier.java:2917)

according this i try this:

java -Xms2000m -cp stanford-ner.jar edu.stanford.nlp.ie.crf.CRFClassifier -prop fa.prop

but the error not fix and i see error again! when i was set a value more than 2000m, my os crashed, or i get this output:

...
...
//stanford log
...

Time to convert docs to data/labels: 8.8 seconds
Killed

how i can fix it

edit:

and for this

[stanford-ner]$ java -Xms1G -Xmx50G -cp stanford-ner.jar edu.stanford.nlp.ie.crf.CRFClassifier -prop fa.prop

i have this error:

[1000][2000][3000][4000][5000][6000]OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f04c7c00000, 1225785344, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 1225785344 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /stanford-ner/hs_err_pid1536.log

Is this really not a duplicate? I mean the answer in that question and the comments to it state perfectly clearly "Try increasing the heap size, maybe it just needs a bit more memory. If not, you likely have some kind of memory leak or inefficient operations that you need to get rid of". I can see the first part done in your question, but the second one is lacking — Ordous
– Ordous, Commented Jul 9, 2014 at 11:47
If -Xmx2048m did not work for you, then try increasing it to -Xmx5G or -Xmx10G or -Xmx30G; else change your program to not hold on to so much memory in the first place. — Chris K
– Chris K, Commented Jul 9, 2014 at 11:47
possible duplicate of What is an OutOfMemoryError and how do I debug and fix it — Raedwald
– Raedwald, Commented Jul 9, 2014 at 11:51
@ChrisK, when i use any value more 2000m i see killed message. — Vahid Kharazi
– Vahid Kharazi, Commented Jul 9, 2014 at 11:51
@28, you can only make that value as large as the OS will allow; typically limited by how much physical memory + swap space you have. — Chris K
– Chris K, Commented Jul 9, 2014 at 12:01

Community · Accepted Answer · 2017-05-23 12:12:57Z

2

Instead of trying with Xms option,

java -Xms2000m -cp stanford-ner.jar edu.stanford.nlp.ie.crf.CRFClassifier -prop fa.prop

try with Xmx as below,

java -Xmx2000m -cp stanford-ner.jar edu.stanford.nlp.ie.crf.CRFClassifier -prop fa.prop

Reference: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space

edited May 23, 2017 at 12:12

CommunityBot

11 silver badge

answered Jul 15, 2014 at 6:47

Vanaja Jayaraman

7813 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

piet.t · Accepted Answer · 2014-07-09 12:32:53Z

1

Looking at the software's purpose it is likely that it is very memory-consuming, so it is reasonable to assume that 1GB of heap just isn't sufficient, so you'll have to further increase your heap-size.

The messages you get when you try imply that you are using

a 32-bit-OS or
a 32-bit-VM

which might both limit you to a maximum heap-size of about 1.5GB (at least on windows).

So make sure you use a 64bit-VM on a 64-bit-OS and then try again to increase the heap-size.

answered Jul 9, 2014 at 12:32

piet.t

11.9k21 gold badges45 silver badges56 bronze badges

Collectives™ on Stack Overflow

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space not fixed

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related