Bug : Audio assets preloading with Firefox 91+ on MacOS

There seems to be an issue with the preloading of audio assets (mp3 and wav) when using Firefox 91 and up on MacOS (tried on several recent MacOS versions)

Issue can be reproduced by launching the “advance loading screen” demo on said target platform :

The loader gets stuck at 50%, there are 2 assets in this sample project including one audio.

Issue does not occur with Firefox 90 or any other browsers on MacOS.

Hi @NicholasOuakam and welcome,

I gave it a try on a Macbook pro running Big Sur, and the example project worked both on an older Firefox version (85.0) and on the latest. Didn’t get stuck or anything.

Are you seeing any errors in the console while that happens?

1 Like

Hi @Leonidas, thank you!

I am not getting any errors in the console. The loading progresses normally until it gets to the audio assets, then no more 'progress; events, no ‘start’ event.
If I uncheck the “preload” option on all audio assets, then the loader completes normally.

This issue occurs for all our projects, when testing using BrowserStack.com. All MacOS versions and Firefox V91 and up.

I can’t repro this issue on https://playcanvas.com/editor/scene/1272702 with Mac OSX 11.6 (20G165) and Firefox 94.0.1 (64-bit)

Just tried BrowserStack and it does lock up on loading :thinking:

Created ticket: https://github.com/playcanvas/engine/issues/3699

I wonder if this can be reproduced outside of Playcanvas as well? Just to try and see if the issue is on Playcanvas side, or Firefox side.

Thanks for the updates

I’m wondering if this might have to do with recent security changes. A couple of my projects failed to load if I accessed the launch page directly from a new window instead of from the editor. This particular project does seem to put out the same errors in the console if I access it via incognito window and then sign in:

Again, not sure if related, but this was new to me this morning. Basis, Ammo, and Platform.js all errored out in the same way on my projects. Maybe it does the same for media assets? I haven’t tried it since all of mine live in a separate S3 bucket.

@yak32 Does what eproasim saying ring any bells?