Environment bug discovered in:
Internet Explorer 11
Flash Fallback being used because of lack of MSE support
While testing this live video test stream :
I encountered first an "Out of Memory" error that caused playback to stall, followed by an error "Invalid offset/length when creating typed array" thrown by this section of the viblast.remuxer.js min file:
When this issue occured, after playback had already stalled, the player/tab of IE crashed and had to be reloaded to even get away from that tab.
I was able to reproduce this issue a few times, but it does not always happen. I presume that it's just IE occasionally maxing out its allotted mem usage from flash and crashing, but might not.
Yes, I believe we upgraded to the 6.20 release last week and haven't had any flash-based issues since then.
Thanks for updating this forum; I'd neglected to respond before amidst the flurry of work.
Did you manage to upgrade and run some tests?
I've been testing the whole day and did not manage to reproduce the issue or notice any memory leakage.
In Viblast Player v6.16 we introduced a lot of optimizations and improvements to our Flash Support so I advice you to update to the latest version - v6.17 and retest.
For me, the issue occured/has occured after 5-15 minutes of Fullscreen use. The system has 8GBs of RAM, with an average of ~4.5GB in use during development and testing.
The version of viblast is viblast|6.15.206167d1 from the viblast.version() call on the page.
I haven't yet reproduced it today, but had done so the few times on that day. It could just be a random issue that my system was having with flash and IE on that day, but not today.
I've been running http://cdn3.viblast.com/streams/hls/airshow/playlist.m3u8 on Win 7 IE 11 for the past 3 hours and cannot reproduce the problem. I will continue testing tonight and tomorrow.
How long does it take you to reproduce the issue - does it occur after 10 minutes, 1 hour, 2 hours? What version of viblast are you running? How many gigabytes of ram does your testing PC have?