Mumble Client NullReferenceException in MumbleClient.AddDecodingBuffer()

[spockTheGrizzly]

Hi,

Thanks so much for making this client! I have brought the latest code from this repo into a brand new Unity project (using version 2021.2.13f1) and have the following error when connecting to a local murmur server on same machine:

The config of my MumbleTester and MumbleMic scripts are as follows:

The client initially connects successfully to the server, but we're unable to send any audio (we use the official Mumble Desktop app to verify this).

The error above shows up almost immediately on startup and then not too long after we get disconnected from the server without the mumble client even noticing that we're disconnected. To be sure, I went back to an older Unity version where I'm confident this client worked back in 2021, but now it doesn't even work in that version.

What could be causing this?

Thanks so much for your help!

Cheers,
Danrae

[Bananahavoc]

Hmm, any chance that you could try with a non-localhost murmur server?

[spockTheGrizzly]

Hmm, any chance that you could try with a non-localhost murmur server?

Thanks for the quick response - yes, I tried with a non-localhost (remote) murmur server and saw the same thing. I've also tested that the servers (local & remote) can receive connections from the official mumble clients.

Also, in both cases (local vs. remote server), I see this error when I exit in Unity:

Cheers,
Danrae

[Bananahavoc]

It looks like AllUsers ends up populated with a null entry. Could you add a check in MumbleClient.cs ln 252 for if newUserState is null? If so, maybe send a screenshot of a log so that we can see the stack trace

[spockTheGrizzly]

I set a breakpoint in the debugger and could see that newUserState is never null (it actually contains the info for each user on the server as expected too) and line 252 in MumbleClient.cs executes as expected.

Something else interesting is, maybe less than a minute after the client gets disconnected from the server, I see this new warning about a UDP error + switching to TCP show up:

I enabled the debug logs in Unity console for you and I believe the stack trace is showing for all the errors in the previous comments. The stack trace in this image is for the new 'switching to TCP' warning I noticed.

[Bananahavoc]

Oh wait, it might be that you don't have EventProcessor in the scene. Can you add that script to the same object as MumbleClient?

[spockTheGrizzly]

Oh wait, it might be that you don't have EventProcessor in the scene. Can you add that script to the same object as MumbleClient?

OMG that was it haha! I'm able to connect and chat on the server now!

The latter error related that was happening when I exited the app was fixed when I rolled back to the following commit: 200cf22

Thanks so much for all your help! And for this repo - it's really an incredible contribution you've made to the open-source community. I added a 'star' in case that helps you somehow haha.

Best regards,
Danrae

[Bananahavoc]

Thank you for the kind words! Means a lot to me.

I'm going to leave this open, there should be a better error log for when the event processor is not in. If you wanted to do a PR for that, would be helpful!

[spockTheGrizzly]

For sure! B.c. it's a work project, I need to get an approval, but I'll drop a patch here either way (maybe from my personal account, worst case). Thanks again!