Bug - Cannot Reproduce java.lang. OutOfMemoryError

[holatuwol]

Hm, looks like a memory leak resulting from constantly reloading the main KoLmafia interface. Not sure if r9189 completely resolves it, but in case it doesn't, you could run your spading army with --CLI instead of using the KoLmafia GUI interface to work around the memory leak.

 

[bumcheekcity]

Thanks for letting me know. I'll try using the CLI if it's still struggling.

 

[Veracity]

Status? You've had six days to try this out. How's it working?

 

[bumcheekcity]

Ah, sorry. Should have said. I've unfortunately not been able to try this out yet. I'm unable to access the separate PC on which I run the Kolmafia code because I'm working on an away job for a couple weeks. I'll keep you updated as soon as I can do more testing.

Edit: I've got my access back to give this a test. I'm running it overnight so I'll let you know in the morning.

 

[bumcheekcity]

Sorry about the massive delay in getting back on this. RL gets in the way. It's still using all the available memory. I have attached a heap.bin here:

http://hotfile.com/dl/116000294/2532a30/heap.7z.html

 

[jasonharper]

Does 37 sound right as the number of logins you managed before running out of memory? There's that many instances of KoLDesktop in your heap dump, each retaining a bunch of GUI-related objects. CLI mode seems like a reasonable thing to try; any actual fix for this problem appears to be deep in hola territory.

 

[bumcheekcity]

37 logins would be probably about correct, yes. I'll run in CLI mode as a solution from here on in.

 

[holatuwol]

Memory leak that kept the 37 instances of KoLDesktop in memory should be resolved in 10048. Or at least, when I hit the GC button, everything other than the current KoLDesktop got garbage collected.

 

[roippi]

Is this resolved?

 

[Veracity]

Almost a year after the OP's last comment in this thread and over a month after a request for an update, no response.
Closing.