game ran out of memory while taking a massive blueprint

zfoxfire · May 12th 2017

This happened after trying to capture a massive set of dungeons underground. the game was freezing up frequently as I flew around the perimeter. the crash happened after setting a name. the blueprint had over 100,000 blocks. not sure how many construction objects (less I assume). I recall the theoretical limit being 1,000,000.

Windows 10 (x64) 10.0 Java: 1.8.0_91 amd64 0.8.2.4_36
Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, X99-A/USB 3.1, 16284 MB (1037 MB Heap)
NVIDIA GeForce GTX 960 20170209000000.000000-000 21.21.13.7866
______________________________________________________________________
Uncaught exception thrown in Thread[jME3 Main,10,main]
java.lang.OutOfMemoryError: Java heap space
at commons.util.Utils$ByteUtils.shortArrayToByteArray(SourceFile:1497)
at commons.util.Utils$ConversionUtils.blocksToByteArray(SourceFile:1073)
at commons.util.Utils$ConversionUtils.blueprintToByteArray(SourceFile:1227)
at U.b.a(SourceFile:121)
at u.c.onButtonReleaseEvent(SourceFile:1937)
at de.jiw.gui.elements.Button.onMouseButtonEvent(Button.java:432)
at de.jiw.gui.core.Screen.onMouseButtonEvent(Screen.java:1660)
at com.jme3.input.InputManager.processQueue(InputManager.java:831)
at com.jme3.input.InputManager.update(InputManager.java:907)
at commons.JIWApplication.update(SourceFile:297)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.runLoop(LwjglAbstractDisplay.java:151)
at com.jme3.system.lwjgl.LwjglDisplay.runLoop(LwjglDisplay.java:197)
at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:232)
at java.lang.Thread.run(Thread.java:745)

zfoxfire · May 12th 2017

btw, not expecting a miracle here. i realize i pushed a limit but one must try to catch an uncaught exception.

Minotorious · May 12th 2017

well played fox...you broke the game again hahaha

red51 · May 12th 2017

Unfortunately the game was only able to allocate 1 GB of memory, which isn't sufficient in many situations... the standalone has no automatic memory assignment (unlike the Steam version), so you either have to assign more memory to it manually, or alternatively you can use the exe which is attached to this post (which assigns 6 GB to the game)

MarcosRC · May 12th 2017

Quote from zfoxfire

one must try to catch an uncaught exception

http://images.shirts.com/produ…ch-them-all-t-shirt-l.jpg

zfoxfire · May 12th 2017

I prefer this one

MarcosRC · May 12th 2017

Hahaha! Good one!

zfoxfire · May 12th 2017

Quote from red51

Unfortunately the game was only able to allocate 1 GB of memory, which isn't sufficient in many situations... the standalone has no automatic memory assignment (unlike the Steam version), so you either have to assign more memory to it manually, or alternatively you can use the exe which is attached to this post (which assigns 6 GB to the game)

Thanks for the info. I was wondering why the performance was unusually low.

Participate now!