Game closes shortly after loading up and playing.

[Hadehariast]

I've developed this same problem tonight. Game ran fine the last time I played (12 hours ago). No new software downloaded in the mean time.

I click "Play" from the website.

Tonight when I clicked "Play", it downloaded some sort of game update following my usual Java security prompt. After that, I've been having crashes every few seconds. Memory usage on the jp2launcher goes up to around 1.5GB and then crashes.

I've downloaded the latest Java update for both 32-bit and 64-bit, and downloaded the latest drivers for my video card. Restarted computer. Makes no difference. Problem still happening.

Specs: Win7 Ultimate 64-bit, Intel i5-2500K processor, 16 GB RAM, nVidia GeForce GTX 750 Ti with 2 GB dedicated memory. Also have 8 GB shared system memory available.

Java Crash Dump:

java.lang.RuntimeException: haven.BGL$BGLException: haven.GOut$GLOutOfMemoryException: GL Error: 1285 (out of memory)
at com.jogamp.common.util.awt.AWTEDTExecutor.invoke(AWTEDTExecutor.java:58)
at jogamp.opengl.awt.AWTThreadingPlugin.invokeOnOpenGLThread(AWTThreadingPlugin.java:103)
at jogamp.opengl.ThreadingImpl.invokeOnOpenGLThread(ThreadingImpl.java:206)
at javax.media.opengl.Threading.invokeOnOpenGLThread(Threading.java:172)
at javax.media.opengl.Threading.invoke(Threading.java:191)
at javax.media.opengl.awt.GLCanvas.display(GLCanvas.java:528)
at haven.HavenPanel$6.uglyjoglhack(HavenPanel.java:455)
at haven.HavenPanel$6.run(HavenPanel.java:490)
at java.lang.Thread.run(Unknown Source)
Caused by: haven.BGL$BGLException: haven.GOut$GLOutOfMemoryException: GL Error: 1285 (out of memory)
at haven.BufferBGL.run(BufferBGL.java:46)
at haven.HavenPanel.redraw(HavenPanel.java:401)
at haven.HavenPanel$1.display(HavenPanel.java:103)
at jogamp.opengl.GLDrawableHelper.displayImpl(GLDrawableHelper.java:649)
at jogamp.opengl.GLDrawableHelper.display(GLDrawableHelper.java:633)
at javax.media.opengl.awt.GLCanvas$9.run(GLCanvas.java:1271)
at jogamp.opengl.GLDrawableHelper.invokeGLImpl(GLDrawableHelper.java:1103)
at jogamp.opengl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:978)
at javax.media.opengl.awt.GLCanvas$10.run(GLCanvas.java:1282)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: haven.GOut$GLOutOfMemoryException: GL Error: 1285 (out of memory)
at haven.GOut.glexcfor(GOut.java:129)
at haven.GOut.checkerr(GOut.java:137)
at haven.BGL$1.run(BGL.java:90)
at haven.BufferBGL.run(BufferBGL.java:44)
... 22 more

[Granger]

In case any of you have 32 bit java on your systems: please deinstall (and install a 64 bit version if no java is left after removing the 32bit ones).

[viznew]

this happening to me also windows update then cant play

[Granger]

this happening to me also windows update then cant play

Just checked on my system: January 2017 windows security update ready for install - will install it and see if it destroys my system too. brb.

[Kearn]

i'm not sure what exactly the problem is, but upon first loading the game hafen uses about 700mb. the moment i take a step, however, it suddenly spikes to 800-900 mb. every consecutive movement, even if walking back and forth in the two tiles, adds about 100 mb each time, growing progressively laggier and more unresponsive until finally crossing 1.5GB and exploding into flames

i was not having this problem or anything close before today, or even this morning. this just began to happen this afternoon.

e: it also appears to be nearly maxing out its CPU allotment

[Hadehariast]

Just checked on my system: January 2017 windows security update ready for install - will install it and see if it destroys my system too. brb.

Quick note-- my update wasn't a Windows Update! When I launched Haven, it spent some time downloading some sort of change to Haven (the same way it does on any update that gets rolled out). I don't know if Jorb or Loftar updated something behind the scenes and released it, but that would make sense.

[inlinebiker]

It's possbile that I am running something else. However everything to my knowledge would be closed. I can definitely see if a restart will do it for me. I have not installed anything else since then. Also I am not entirely sure what java I am running. It is java 8 is all I know.

[MagicManICT]

Quick note-- my update wasn't a Windows Update! When I launched Haven, it spent some time downloading some sort of change to Haven (the same way it does on any update that gets rolled out). I don't know if Jorb or Loftar updated something behind the scenes and released it, but that would make sense.

It actually does this any time files in the cache become out of date or are lost. (It is a file cache, after all.) It wouldn't surprise me either way if it was a Windows problem or a small client update causing issues. I haven't logged in yet today.

[Hadehariast]

Update: I've uninstalled Java 32-bit, and launched Haven via the "Play" button. Problem still happening-- but this time I got up to 1.7 GB memory usage on jp2launcher before I decided to logout before it crashed again. Inside caves the problem isn't bad-- it sticks around 500 MB usage. Outside is another story though.

MagicManICT-- I also deleted my cached version of Haven as well and re-downloaded it since this started happening. No luck!

[Kearn]

okay, i experimented a bit. how fascinating.

if i log in and IMMEDIATELY log out in the settings window, memory usage remains frozen at 1.3GB in the logout menu and then continues to increase after logging in again. there seems to be an enormous leak of some kind.

e: actually, i can't even log back in again. the memory is burned through so fast it crashes before it can even load the map again.
e2: it also keeps randomly logging me out without warning if i simply stand still for more than 15 seconds