Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
Kagami opened this issue Aug 29, 2015 · 3 comments
Open

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

Kagami opened this issue Aug 29, 2015 · 3 comments
Labels
not our bug research

Comments

@Kagami
Copy link
Owner

Kagami commented Aug 29, 2015

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.
@bvibber
Copy link

bvibber commented Aug 31, 2015

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
Copy link
Owner Author

Kagami commented Aug 31, 2015

Thanks for the info!

@Kagami
Copy link
Owner Author

Kagami commented Mar 19, 2016

This issue seems to be fixed 3 days ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
not our bug research
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bvibber @Kagami