mchristos / checkers Goto Github PK

The game logic remains same, did not change data structures. Before match starts, constant memory is around 100MB. (Both 32 & 64bit java). As match goes on, the RAM usage spikes up! ⬆️

The RAM usage on 64 bit Java (tested on all major OS, and Java 8 latest and 17) is very high! Hovering around 260-390MB during single match. You may want to investigate this. Maybe too much copying of Heavy objects, eg BoardState

@Mchristos When playing against AI, after the AI did a double jump, i got NPE in the console as follows. it seems it is coming from line 192 of BoardState. I had not modified the original code.

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException: Cannot invoke "org.davistiba.game.Piece.getPlayer()" because the return value of "org.davistiba.game.BoardState.getPiece(int)" is null
	at org.davistiba.game.BoardState.getSuccessors(BoardState.java:192)
	at org.davistiba.game.BoardState.getSuccessors(BoardState.java:170)
	at org.davistiba.game.Game.getValidMoves(Game.java:79)

The game logic remains same, did not change any data structures. Before match starts, constant memory is around 100MB. (Both 32 & 64bit java). Once start moving the pieces and match goes on, the RAM usage spikes upto 600 MB and hovers around 400~500MB throughout the match.

Tested on Windows 10, MacOS Sonoma. JDK 17.0.6 and JDK8u361