Out Of Memory?

[CSPAN]

Pretty new, also, had this topic moved to Wizards Tower in old thread, but after noticing it happens with the vanilla client, thought Id post it here.

Starts with 60 fps, then after an amount of time that varies, will crawl to 0 fps, then crash.

restarting the client fixes temporarily.

pls help

pls delete old thread

Code: Select all

java.lang.OutOfMemoryError: Java heap space
   at com.jcraft.jorbis.DspState.init(DspState.java:190)
   at com.jcraft.jorbis.DspState.synthesis_init(DspState.java:216)
   at dolda.xiphutil.VorbisStream.<init>(VorbisStream.java:98)
   at dolda.xiphutil.VorbisStream.<init>(VorbisStream.java:117)
   at haven.Resource$Audio.stream(Resource.java:1410)
   at haven.AudioSprite$ClipSprite.<init>(AudioSprite.java:70)
   at haven.AudioSprite$1.create(AudioSprite.java:49)
   at haven.Sprite.create(Sprite.java:124)
   at haven.Gob.ctick(Gob.java:108)
   at haven.OCache.ctick(OCache.java:68)
   at haven.Glob.ctick(Glob.java:200)
   at haven.HavenPanel.run(HavenPanel.java:527)
   at java.lang.Thread.run(Unknown Source)

[shubla]

You are (obivously) running out of ram.
Either your computer doesnt have enough free ram avaible, or then not enough of it is assigned to jav a.
But i think it should work even if you'd not assign very much to java.

[MagicManICT]

It's not a system ram issue as you're implying, shubla, unless it is a very old computer, and then the issue would be that there isn't a support graphics processor even if this one is resolved.

First thing to try is increasing the available heap size. This may or may not fix it. You can do this in two ways: modifying the .jnlp file (open with a text editor, find "max-heap-size" and double the number after it; be sure to leave the M and inside the quotation marks; be sure to use a copy you saved to the desktop or such and launch from that), modify the batch file that launches haven.jar (look for a -xmx and/or -xms argument and change the number values on that). If this fixes it, great.

Otherwise, it looks like the crash is related to the recent change to audio buffers loftar implemented. If you increased those to a point of running out of memory, you may need to clear cache and any configuration files that got modified and download again if adjusting numbers doesn't work.

Please let me know if I need to type this up better. I can do a better step-by-step.

[Granger]

Please post the info needed about your system, see viewtopic.php?f=47&t=39954

[CSPAN]

Latest version of Java, 8gigs of RAM, Windows 10, GeForce GT 720. @MagicMan, will give that a try.

[APXEOLOG]

Ensure that you have proper Java installed (64-bit for 64-bit system)

[jorb]

Paged loftar.

[loftar]

I don't think there's any way for me to tell what is happening without a heap dump. If you can produce a heap dump when the client is on the verge of crashing, that would be very helpful.

[romovs]

^ Translation to English:
Get this https://dl.dropboxusercontent.com/u/371 ... -debug.zip and use run.bat
Once it crashes send java_pid*.hprof file to loftar.

[CSPAN]

Pm'd