Second run in the same worker cause "Out of memory" in Edge #8
Description
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.