If you build with MAXIMUM_MEMORY=-1 that means "no specified limit". In that case I think each browser should allow growth as much as it possibly can.
(see src/settings.js for MAXIMUM_MEMORY for more details, including why the default is 2GB and not -1, but basically, -1 has some minor code size downsides) On Thu, Oct 1, 2020 at 6:25 AM Brian Gavin <[email protected]> wrote: > Now that Firefox supports wasm pthreads. I would like to avoid having to > make 2 versions of our WASM module. Chrome supports a max memory of ~4GB > and Firefox ~2GB. Is there a way for me to have a different value for > MAXIMUM_MEMORY based on the browser. I am using it with pthreads and > memory growth turned on. > > Thanks > Brian Gavin > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/2bd79de4-65bc-445b-8dac-e8bd8bb6c802n%40googlegroups.com > <https://groups.google.com/d/msgid/emscripten-discuss/2bd79de4-65bc-445b-8dac-e8bd8bb6c802n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpR07C03sh%2BCAo0WLTjWMU5JJuQHX1DUrJsqUBEpbN7T%3Dw%40mail.gmail.com.
