Second run in the same worker cause "Out of memory" in Edge

Question

Second run in the same worker cause "Out of memory" in Edge

Kagami opened this issue 9 years ago · comments

For some reason Edge doesn't like the second run of main function in the same worker and cancels it with Out of memory. Interesting enough, IE11 works fine in that case. It might be result of bug in current implementation of asm.js in Edge.

This can be workarounded by respawning Prober's worker on each run of analyze and decode methods. While it's rather ok to respawn analyzer to be safe against already running issues, it will make software player even slower.

Brooke Vibber · Answer 1 · Tue Sep 01 2015 00:45:30 GMT+0800 (China Standard Time)

This is a bug in Edge's asm.js optimizations: https://connect.microsoft.com/IE/feedbackdetail/view/1721733/asm-js-modules-can-only-be-executed-once-with-asm-js-optimizations-enabled

Kagami · Answer 2 · Tue Sep 01 2015 00:50:53 GMT+0800 (China Standard Time)

Thanks for the info!

Kagami · Answer 3 · Sat Mar 19 2016 21:50:09 GMT+0800 (China Standard Time)

This issue seems to be fixed 3 days ago.