Repeatable out of memory errors about tectonicus HOT 11 CLOSED

From [email protected] on September 19, 2012 09:28:46

Tectonicus 2.14 and the myconfig.xml file does work properly on a Mac mini with 4G/OS 10.7.4/Java 1.6._35. It takes a loooong time and brings the Mac to its knees, but it runs to completion and produces a correct map.

I've been doing more research on the proper format for the myconfig.xml file. There are multiple sources of information, mainly on or accessible via the Minecraft wiki, which unfortunately conflict with each other. I've cleaned it up a lot. I've attached the latest file that is working on the Mac. It's called myconfig-mac.xml. I've converted it back to use my PC pathnames, and that's testing now.

This last is probably a non-issue since Tectonicus 2.14 isn't officially compatible with Minecraft 1.3.x. However, if I try to use biome colors, Tectonicus generates an error that it can't de-obfuscate minecraft.jar. This is true with a plain, vanilla minecraft.jar.

Thanks!

Attachment: myconfig-mac.xml

from tectonicus.

From [email protected] on September 19, 2012 10:25:59

Update with the PC test. The same error occurred after tile 11944 of 121926. XML and log are attached.

Attachment: myconfig-macbased.xml TectonicusLog-macbased.txt

from tectonicus.

From [email protected] on September 19, 2012 11:25:18

I should have mentioned that this last Windows 7 run was with an empty output directory. No cache from previous runs was used.

from tectonicus.

From [email protected] on November 14, 2012 11:03:33

I was able to reproduce this frustrating issue as well, and a search online brought me here.

I also think that I figured out how to solve the problem. When running tectonicus without the -xms or -xmx memory switches, the out of memory issues disappeared. I recommend running tectonicus without these switches.

I'm guessing that tectonicus calculates its memory requirements based on how much physical RAM the host machine possesses instead of how much tectonicus is allocated via the JVM. If so then this ought to be fixed.

from tectonicus.

From [email protected] on September 19, 2013 19:42:14

I am running into this issue as well, however removing the Xmx/Xmx parameters didn't help. It occurs roughly every 5k tiles (thats using ~3.5G memory, system as 4G total).

from tectonicus.

From [email protected] on September 22, 2013 02:50:55

Reproduced on my machine as well, running windows 8.1 64bits with 8gb of ram

from tectonicus.

From [email protected] on November 12, 2013 14:31:33

Reproduced on my machine as well, running windows 8.1 64bits with 16gb of ram

from tectonicus.

From skoeven on November 12, 2013 15:28:08

For anyone experiencing out of memory errors, please post your config file and log file so we can get an idea of what might be causing the problem.

Status: Accepted

from tectonicus.

From [email protected] on January 21, 2014 01:34:10

Log file and config file attached, I'm not passing any special options to the JVM.

From my reading it sounds like the JVM isn't garbage-collecting direct byte buffers in a timely fashion, so even if you aren't leaking them they have a tendency to build up, and that's problematic because the JVM can't detect the nearly-out-of-native-memory condition to run a GC cycle. You might need to try and force the JVM to GC your LWJGL objects.

Attachment: TectonicusLog.txt LauraConfig.xml

from tectonicus.

From [email protected] on January 21, 2014 01:54:45

Also, for people having this problem, messing with the -XX:MaxDirectMemorySize parameter for the JVM might help.

from tectonicus.

This may not be as much of an issue with modern machines and modern Java versions. Closing.

from tectonicus.