Unity Issue Tracker - Crash on LightProbesManager::GetLightProbeJobData when entering the Play Mode

Duplicate

Votes

0

Found in

2020.3.46f1

2021.3.20f1

2022.2.9f1

2023.1.0b7

2023.2.0a5

Issue ID

UUM-29017

Regression

No

Crash on LightProbesManager::GetLightProbeJobData when entering the Play Mode

--

-

Mar 03, 2023

Reproduction steps:
1. Open the attached “LightProbes.zip” project
2. Open the “Assets/Main.unity” Scene
3. Enter the Play Mode

Expected result: Editor doesn’t crash
Actual result: Editor crashes

Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.0a9
Not reproducible with: 2022.2.0a10, 2022.2.9f1, 2023.1.0b7, 2023.2.0a5

Reproducible on: Windows 10 (21H2)

First few lines of the stack trace:
0x00007ff6334e9641 (Unity) LightProbesManager::GetLightProbeJobData
0x00007ff6334e4f20 (Unity) ComputeTetrahedralization
0x00007ff632be0556 (Unity) LightProbes_CUSTOM_TetrahedralizeAsync
0x000002527465cf31 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.LightProbes:TetrahedralizeAsync ()
0x000002527465e4ab (Mono JIT Code) [Main.cs:133] Main:OnSceneUnloaded (UnityEngine.AsyncOperation)
0x0000025274659f3c (Mono JIT Code) UnityEngine.AsyncOperation:InvokeCompletionEvent ()

This is a duplicate of issue #UUM-13497

Crash on LightProbesManager::Append when unloading Scene Async that contains light probes and calling light probes Tetrahedralize Async

Resolution Note:

Thanks for submitting this issue!
This has already been fixed in the most recent (2022.3) LTS as part of a refactoring of the LightProbesManager. This refactoring will not be backported to earlier versions of Unity as it significantly changes behavior.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-13497

Log in to vote on this issue

Search Issue Tracker

0