Well, "function signature mismatch" doesn't look like a memory leak 
#Raid Memory Leak
vagrant fossil
Does it happen consistently (with this traceback)? If so, then it's rather 1) some low-chance rng gets triggered for whatever reason (thus the function is called, which is omitted otherwise) or 2) some weird logic applied after X raid runs (UPD: hmm, for example some kind of cleanup?)
jade bobcat
It happens consistently somewhere between 15 and 25 runs. And really only with lots of raids. Again, I’m not a game dev, just a regular dev, but wasm is relates to web assembly and how it connects to unity. So maybe it is just a web issue, not the infamous memory leak.
languid quartz
interesting! /til