Search Issue Tracker

Fixed

Fixed in 6000.1.14f1, 6000.2.0b13, 6000.3.0a3

Votes

0

Found in

6000.2.0b8

Issue ID

UUM-111154

Regression

Yes

Crash on InputExtraction::ExtractOOTSSnapshot when opening a specific Scene

-

Steps to reproduce:
1. Open the “user’s attached project”
2. Open the "Assets/Crypt Dungeon Environment/Rooms/Crypt/Scenes/crypt.unity" Scene
3. Observe the crash

Reproducible with versions: 6000.2.0a8, 6000.2.0b10, 6000.3.0a2
Not reproducible with versions: 6000.0.54f1, 6000.1.12f1, 6000.2.0a7

Reproducible on: macOS 15.5 (M1 Max), Windows 11 (by the reporter)
Not reproducible on: no other environment tested

Note:
* The scene is set to Bake Lighting on Load

First few lines of StackTrace:
{noformat}
#0 0x0000010471a9d8 in InputExtraction::ExtractOOTSSnapshot(UnityGUID const&, core::vector<PPtr<MeshRenderer>, core::allocator<PPtr<MeshRenderer>, 0ul>> const&, core::vector<PPtr<Terrain>, core::allocator<PPtr<Terrain>, 0ul>> const&, core::unique_ptr<JobQueue>&, SceneLights&, InputExtraction::OOTSSnapshot&)
#1 0x000001046c2230 in BakePipeline::Driver::Update(GISceneManager&, BakePipeline::Driver::BakeAnalytics const&, bool)
#2 0x000001046b66e4 in BakePipeline::RuntimeManager::Update(bool&)
#3 0x00000104684558 in BakedGISceneManager::PostUpdate()
#4 0x000001046a5998 in gi::PostUpdate(core::vector<GISceneManagerClient*, core::allocator<GISceneManagerClient*, 0ul>> const&){noformat}
{noformat}
0x00007FFE3435C590 (Unity) memcmp
0x00007FFE326C93EF (Unity) operator==
0x00007FFE327E29BF (Unity) SetTextureImporterSettings
0x00007FFE328701B6 (Unity) MoveTextureSnapshotsToAssetsFolder
0x00007FFE3286EBAE (Unity) WriteLightingDataAssetJob::Integrate{noformat}

Add comment

Log in to post comment