Yolp

@dijs no problem if you don't have time to fix this, but can you please answer my question?

This also affects the NPM Firebase client when running it on a React Native app on an iOS device. Seems the default Javascript Engine of React Native on iOS is...

> Just to let you know, it will probably take some time for us to come up with some way to mitigate this, it probably requires some significant changes. In...

Yes my workaround applies to React Native only. React Native on iOS uses the Safari Javascript Engine by default. This is like Safari without a DOM. If the Firebase client...

> Thanks for sharing your solution. I do not understand your last comment, are you suggesting there is a potential easy fix we should explore? If yes, I'd like to...

> @yolpsoftware Thanks. We did not allocate more memory on Safari than other browsers, it seems Safari simple allocate more memory for the same set of documents. The only place...

@wu-hui I really would like to know whether we can consider Firebase to be something that works across all current platforms and devices. If you say, well, we can't fix...

> That being said, we do have someone assigned to this to further isolate the issue now, we will update this thread when we have something. @wu-hui thank you, that's...

@hirbod thanks for the analysis. This makes very much sense. I didn't know about the system limit. Would you agree that it would be very nice of Expo (or React...

@hirbod I had the time to check this thoroughly. In my app, I get the error even when at most 2 audio files are decoded / preloaded at the same...