Memory Leak
Closed this issue · 1 comments
fsparv commented
In other entirely NOT shocking news, the code I wrote 15 years ago when I was first learning java seems to have a memory leak...
51 (A3) Move:A3
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x000000079b500000, 572522496, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 572522496 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /home/gus/leelaz/leela-zero/hs_err_pid89296.log
fsparv commented
It's worth noting that this was found after running for several days straight. The ever scrolling move list in the UI is of course a leak of sorts. I'm not sure this is worth the time to track it down and fix it. This can be reopened if such things become more common. Even starting with -Xmx10mb is running fine for several games now. It's also possible that the move to stateless rule implementations has helped.