b__0_0 () (at ./Library/PackageCache/com.unity.netcode.gameobjects@9684ced5879f/Runtime/Core/NetworkUpdateLoop.cs:214)
```
I’ve added a couple of log messages to `UpdateServerClientSceneHandle` to see when the scene handle mappings get populated and it looks the `ClientSceneHandleToServerSceneHandle` is populated too late (its populated right after this exception), which leads me to believe that scenes are now synchronized too late or incorrectly.
The way I reproduced this in my project (`Scene 1` in this case is my bootstrap scene, always loaded after the game starts):
- `Client A` starts a `Session A` in (`Scene 1`, `Scene 2` (additive, active)).
- `Client B` starts a `Session B` in (`Scene 1`, `Scene 3` (additive, active)).
- `Client B` leaves `Session B` and starts loading another set of scenes (`Scene 1`, `Scene 2` (additive, active)).
- Right after the scenes are finished loading, `Client B` starts joining `Session A`.
- `Client B` gets `KeyNotFoundException` log message.
- `Client A` (session owner) gets `CMB Services` log message.
- The network session is in broken state where `Client B` sees `Client A` (session owner) locked in place and `Client A` doesn’t see `Client B`.
Some details:
- Unity `6000.0.47f1`.
- Multiplayer Play mode `1.3.3`.
- Using sessions API.
- I did not update any other packages prior to trying out `v2.4.0`.
- Distributed Authority.
- Session owner uses `CreateSessionAsync`.
- Client uses `QuerySessionsAsync` and then passes the id to `CreateOrJoinSessionAsync`.
---
### Author:  [@NoelStephens\_Unity](https://discussions.unity.com/u/NoelStephens_Unity)
#### Post date: [June 6, 2025, 5:48pm UTC](https://discussions.unity.com/t/netcode-for-gameobjects-2-4-0-released/1651980/3 "2025-06-06T17:48:24Z")
> [@EdEddnEddy](#):
>
> `Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak`
This issue was discovered just shortly after v2.4.0 was made public and has a pending fix for it in [PR-3486](https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/pull/3486). The fix for this will be released in a patch soon. The memory leak itself is roughly the `size of a ulong` \* `number of connected clients`. So, it is a relatively small leak that happens once per non-session owner connecting to an existing session…but will be resolved very soon.
The other issue I am looking into today.
---
### Author:  [@NoelStephens\_Unity](https://discussions.unity.com/u/NoelStephens_Unity)
#### Post date: [June 9, 2025, 9:08pm UTC](https://discussions.unity.com/t/netcode-for-gameobjects-2-4-0-released/1651980/4 "2025-06-09T21:08:12Z")
> [@EdEddnEddy](#):
>
> The session owner gets this error message as the client connects:
I believe [PR-3491](https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/pull/3491) should resolve this issue.
If you have time, try using this branch and see if it resolves the issue on your side?
```auto
"com.unity.netcode.gameobjects": "https://github.com/Unity-Technologies/com.unity.netcode.gameobjects.git?path=com.unity.netcode.gameobjects#fix/reset-networkclient-completely-upon-shutdown",
```
This will be included in an up-and-coming patch.
---
### Author:  [@EdEddnEddy](https://discussions.unity.com/u/EdEddnEddy)
#### Post date: [June 10, 2025, 12:53pm UTC](https://discussions.unity.com/t/netcode-for-gameobjects-2-4-0-released/1651980/5 "2025-06-10T12:53:05Z")
> [@NoelStephens\_Unity](#):
>
> ` "com.unity.netcode.gameobjects": "https://github.com/Unity-Technologies/com.unity.netcode.gameobjects.git?path=com.unity.netcode.gameobjects#fix/reset-networkclient-completely-upon-shutdown",`
Just tested this now, I can confirm that the bug I mentioned earlier, including the warnings related to leaks are no longer there!
---
### Author:  [@NoelStephens\_Unity](https://discussions.unity.com/u/NoelStephens_Unity)
#### Post date: [June 10, 2025, 3:07pm UTC](https://discussions.unity.com/t/netcode-for-gameobjects-2-4-0-released/1651980/6 "2025-06-10T15:07:31Z")
Thank you for providing the issue and for verifying the fix on your end.
It is much appreciated!
These fixes will follow the pending v2.4.1 update (primarily internal house keeping adjustments) most likely as v2.4.2 (_exact version TBD_).
---
### Author:  [@michal\_chrobot](https://discussions.unity.com/u/michal_chrobot)
#### Post date: [June 17, 2025, 8:45am UTC](https://discussions.unity.com/t/netcode-for-gameobjects-2-4-0-released/1651980/7 "2025-06-17T08:45:45Z")
Hey, as a follow up, **NGOv2.4.2** is already released ([CHANGELOG](https://docs.unity3d.com/Packages/com.unity.netcode.gameobjects@2.4/changelog/CHANGELOG.html#242---2025-06-13)) which contains all the fixes mentioned before in the thread.
We would also like to point out that **NGOv2.4.1** ([CHANGELOG](https://docs.unity3d.com/Packages/com.unity.netcode.gameobjects@2.4/changelog/CHANGELOG.html#241---2025-06-11)) contained a bunch of structure updates so remember that **if you are utilizing TestHelpers** then follow the instruction from the CHANGELOG
> If your project is using the `Unity.Netcode.TestHelpers.Runtime` assembly then you need to switch `asmdef` references to `Unity.Netcode.Runtime.Tests` .
_Happy Netcoding!_
---
### Author:  [@michal\_chrobot](https://discussions.unity.com/u/michal_chrobot)
#### Post date: [June 27, 2025, 1:23pm UTC](https://discussions.unity.com/t/netcode-for-gameobjects-2-4-0-released/1651980/8 "2025-06-27T13:23:46Z")
Quick mention that [NGOv2.4.3](https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/releases/tag/v2.4.3) was released as a response to issue reported **[HERE](https://discussions.unity.com/t/network-objects-dont-despawn-on-disconnect-even-with-dont-destroy-with-owner-unchecked/1658887/7)** 👈