Regarding the bug people on Linux are experiencing, here is something that seems to fix it for me:
- open data/ENGINE.js in some text editor
- find "this.source.buffer=null," (without quotes, but including the comma); it only occurs once, at line 1 starting around column 43010
- delete it (or comment it out)
I think setting the buffer to null is a bit redundant, as the source is immediately afterward disconnect()'ed, and the buffer shortly later gets assigned this.decodedBuffer. (Though null is supposed to be accepted, so I guess the underlying problem is an outdated web engine.)