Bug FMOD returns error code 36 (FMOD_ERR_INVALID_HANDLE) executing setRelativeAudibility

Error happening to me too. Unity 2022.2.18f1
Makes the game unplayable, so many logs

 

Happening to me too in the latest LTS release . I tried 2022.x some time ago, then had to revert back to a 2021 LTS flavor (.21 in my case) for it and other audio problems to go away. When I saw in the 2022 LTS patch notes that it had supposedly been resolved I was guardedly optimistic. I spent all day yesterday dealing with other integration issues before I could build and test, only to find the problem remained. (Totally off topic, but build times also ballooned from 2-3 minutes in 2021, to well over 15 minutes with 2022, while shadows exhibited very strange distortion when rendered in a WebGL build compared to what's visible in the editor. Another deal breaker.) So back to 2021 I go. It's both frustrating and time-consuming to be used as QA by Unity and to forego other valuable features the new "stable" release has to offer. I hate to complain, but... more bodies should be dedicated to WebGL in-house. Even a band-aid solution would be welcome. Using an alpha version, assuming that even works, is not a viable option, and back-porting shouldn't have to be either.

 

Updated my project to Unity version 2023.2.0a17, errors still appear in hundreds as before. But the build size has decreased by 1 MB, at least something...

 

this needs to be fixed, still happening in 2022.3.2f1

 

It's not just an inconvenience, the browser console is being spammed a ton which isn't great for performance...

 

Hello everyone!

Are there any updates on this issue? I Updated my project the the LTS version 2022.3.1f, but the errors still periodically appear and spam the console of the WebGL build.

The errors are

and

Is there a way to just silence the errors in the console?

Thanks in advance for any tipps or inputs on this issue!

Best regards,
Patrick

 

I'm on 2021.3.2f1 and the error persists

 

also happening on 2022.3 LTS. WebGL builds became unplayable after upgrading

 

similar to some of the others posts - the client logs the error out so much it slows to a crawl

 

Trying to get to a repro case because it doesn't happen straight away or consistently.

 

I also have the same problem, and I tried to upgrade from 2022 LTS to 2023.2.0.a20, because I saw that this issue supposedly fixed the problem in 2023.2.0a5.

But I get the same thing, after some playtime, these errors start to get spammed in the browser console, hundreds of them per minute:

./Modules/Audio/Public/AudioSource.cpp(1723) : Error executing dspHead->setRelativeAudibility(relativeAudibility) (An invalid object handle was used. )

FMOD returns error code 36 (FMOD_ERR_INVALID_HANDLE) executing setRelativeAudibility

I also noticed that besides the above errors that are being spammed hundreds of times per minute, Unity 2023.2.0.a20 also started to occasionally show these things in the browser console:

Trying to get length of sound which is not loaded.

Channel.playSoundClip error. Exception: TypeError: Failed to execute 'start' on 'AudioBufferSourceNode': The provided double value is non-finite.

Additionally, I tried to downgrade to Unity 2021 LTS (quite troublesome, since this broke all the Box colliders which now for some reason had their sizes reset to 2). And I got the same errors spammed in the console.

Would be nice to receive a fix for this as fast as possible, since it's affecting one of my released games.

 

The way I "fixed" this, though you cannot really call it a fix, is by preventing the logs regarding that issue from being displayed to the console. This is dumb, but when you waste an entire day trying to fix something like this, where even Unity version upgrades/downgrades don't work, you become quite "creative".

The "fix":

1. In C:\Program Files\Unity\Hub\Editor\2022.3.3f1\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\UnityLoader\UnityLoader.js find this function

print: function (message) {

and just add this there

if(typeof message === 'string' && message.includes("FMOD returns"))return;

2. In C:\Program Files\Unity\Hub\Editor\2022.3.3f1\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\lib\Logging.js find this line

case 4: //LogType_Exception

and just prevent that console.error

if(!str.includes('AudioSource.cpp')) console.error (str);

On the next build, you'll get these fixes in your UnityLoader and Framework files, and you won't see those errors in the console anymore.

 

Preventing the logs prevents the crash over time?

 

This is cheeky. And I love it

 

Well, my game wasn't crashing at all to start with. It was just annoying for me to see all those logs/errors in the analytics service, and to be unable to properly spot any errors in the browser console due to them being spammed there.

But aside from that, I didn't encounter any crashes/audio issues, though the game was indeed lagging a little bit with those errors being spammed, also annoying.

 

I was having this issue when switching from the main menu scene to the game scene, but managed to resolve it by switching from LoadSceneMode.Single to LoadSceneMode.Additive, and then unloading the previous scene asynchronously.

Code (CSharp):

1. private static IEnumerator PreLoadScene(string sceneToLoad, Action<AsyncOperation> onLoaded90PercentAction)
2.     {
3.         yield return null;
4.  
5.         AsyncOperation asyncOperation = SceneManager.LoadSceneAsync(sceneToLoad, LoadSceneMode.Additive);
6.         //Don't let the Scene activate until you allow it to
7.         asyncOperation.allowSceneActivation = false;
8.  
9.         bool hasActivated = false;
10.         while (!asyncOperation.isDone)
11.         {
12.             if (asyncOperation.progress >= 0.9f)
13.             {
14.                 if (!hasActivated)
15.                 {
16.                     onLoaded90PercentAction?.Invoke(asyncOperation);
17.                     hasActivated = true;
18.                 }
19.             }
20.             yield return null;
21.         }
22.     }

I preload the main scene additively, then when it reaches 90%, I start unloading the menu scene asynchronously with

SceneManager.UnloadSceneAsync

and set

asyncOperation.allowSceneActivation = true

(this is passed in through the onLoaded90PercentAction in my example, but you could just hard-code it there instead).

I also needed to call

Destroy()

on the audio listener in the main menu scene, and

Stop()

on the AudioSource when the main scene reached 90% loading.

 

I believe we had some luck mitigating this issue by pooling our AudioSources instead of placing audiosources on any GameObject that wanted to play a sound... But we still see the issue periodically.

 

still this f**cking spam FMOD return. 2022.2.11f1. how this fix?

 

Still an issue on 2022.3.11f1. Release notes for 2022.3.6f1 LTS say it should be fixed:

• Web: Fixed bug in WebGL's FMOD implementation that caused the console to be spammed with errors when using the PlayOneShot API. (UUM-40643)

@SeventhString any news?