Performance and memory is becoming a problem

[icecream17]

While running the tournament "avoider" played against itself....

...and it's soooo slow to update. Update takes soooo long.

[icecream17]

This probably is a combination of:

• Code updating the board more slowly because of all the squares, moveHistory, and gameStates
• Code picking a move more slowly because of all the squares, moveHistory, gameStates
• setTimeout throttling in the async pause function

Eventually in the tournament there's an "Aw, Snap!" (Error 64000) [Google ran out of memory while trying to display the webpage]

[icecream17]

Example

[icecream17]

Did you know that stackoverflow has copyright rules

Credit: Stackoverflow. Question: https://stackoverflow.com/questions/17491022/max-memory-usage-of-a-chrome-process-tab-how-do-i-increase-it, Answer: https://stackoverflow.com/a/41422993 User who answered: https://stackoverflow.com/users/2780791/alexei-check-codidact

[icecream17]

Starting memory: 24 MB
After waiting awhile: 21.4 MB (hooray chrome optimization)
After 20 turns: 22.2 MB
After click "reset game": 22.3 MB
After 101 moves: 51.7 MB

21.4 --> 22.2 after 20 turns (rate = 0.04 MB per turn)
22.3 --> 51.7 after 101 turns (rate = 0.29 MB per turn)

The most memory is probably spent with gameStates and moveHistory

[icecream17]

Starting with commit fad25cf,
and ending with commit b50d235,
after 175 moves the memory is still at 48 MB

[icecream17]

Google says that 15 tabs can take up to
1 GB to 2 GB.

So 67 MB to 133 MB
After 1 whole tournament it's 72.7 MB. Pretty good. This will still be open though.