I hadn't considered this to be a thing that tenuki should solve for. I think my expectation is that removing a board from the page is very likely to require you to handle the empty content in some way, and everyone's needs would be slightly different.

Are you able to keep a handle on the DOM element you gave to the game constructor and remove it from the DOM with, say, remove()?

I had some problems with a memory leak. But maybe if I remove the passed element all event listeners and such will be gone as well? I tried just clearing the innerHTML of that element but that did not seem to fix it.

Still have the same problem. It retains a lot of detached svg elements and event listeners for some reason. Running garbage collection manually does not seem to collect them.

After creating a few of these games the tab becomes really sluggish.

Found the problem. Lines like this have access to the closure of the function that defines them, so the closure for the event handler will keep all references alive from that scope. Since the event is on window the handler will never be collected. Causing it to remain alive and keep everything else in memory.

There is also closures created for requestAnimationFrame. And probably others I haven't found yet.

I am interested in this too - trying to set up a way to practice various joseki repeatedly, and I'm looking for an efficient way to "reset" or remove/recreate the board. Is there any change or workarounds that have arisen in the last few years?