View Single Post
Old 08-28-2019, 09:56 AM   #69
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Assuming the program in question is using recursive descent/parsing techniques, it may not be a total RAM issue or even RAM available to the JVM, but instead a single thread stack size issue. Each recursive call pushes a new frame on the stack with return info and local variables. If that is the case, increasing the stack size (the Xss) may be needed.

This is just a guess, but given the OP has 64gb of ram and is still running into trouble, this may in fact be the cause.

Last edited by KevinH; 08-28-2019 at 10:20 AM.
KevinH is offline   Reply With Quote