Wowza player does not destroy previous instance if new instance comes too quickly

You then get a double playback - and no way to destroy the extra playback without reloading.

So we have to be careful about having good code where this doesn’t happen. I guess this should really be in a bug report.

Uncaught TypeError: Cannot read property ‘destroy’ of null h @ wowzaplayer.min.js:32(anonymous function) @ wowzaplayer.js:1(anonymous function) @ wowzaplayer.js:1

custom.js:1820 that was OK

Hello Alan,

I do apologize for the long delay in replying, and hope that you have already worked through the issue you were facing through our Support Ticket system.

There have been many updates to our Wowza Player since the original date of this post.

Please let me know if you are still having any issues with your deployment of our Wowza Player.

Thanks in advance,

Jason Hatchett