I have a memory-intensive process that runs fine on Firefox (everywhere) and Chrome (Max+Linux) and Safari. However, Chrome on Windows "aw, snap"'s me most-- but not all-- of the time. I was finally able to resolve this with `--max_old_space_size=4096` Chrome command line parameter, but I don't want to place this requirement on my users.
My guess is that gc is not keeping up with me on Windows in particular (fewer points where gc wants to run? ) or else that the defaults differ per platform. Any ideas about how to nudge garbage collection to happen more often? Any other thoughts? Thanks! -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
