Editor hard-crashes when baking Scenes with LightBaker

Unity: Progressive Lightmapper

Fixed

2023.2.X

2023.1.X

2023.1.0b5 onwards

Resolved with this PR: https://github.cds.internal.unity3d.com/unity/unity/pull/25580

Resolved with this PR: https://github.cds.internal.unity3d.com/unity/unity/pull/25839

Repro:

Download and import the attached repro project: here
Open the Scene "APVStudy_Test01".
Navigate to the Lighting Window. Press "Generate Lighting".

Note:

The editor hard-crashes with 100% reproduction. The logs can be found: here

There is also an error posted to the console:

[Internal link]

Observed:

After bisecting the Scene, an interesting problem emerges. It is possible to bake with no geometry. With only the lightmapped, apartment geometry. With only the 3D props. However, when both the apartment geometry and and props are enabled, then we have a hard crash.

========== OUTPUTTING STACK TRACE ==================
0x00007FF9116AA937 (Unity) RadeonRaysMeshManager::AddInstance
0x00007FF9116E8240 (Unity) RadeonRaysJobAddInstance::Execute
0x00007FF9115CBFFC (Unity) `anonymous namespace'::ExecuteJob
0x00007FF9115CF0A3 (Unity) LightBaker::Prepare
0x00007FF9115CACE0 (Unity) LightBaker::Bake
0x00007FF911567ACE (Unity) `anonymous namespace'::RunBake
0x00007FF91020121D (Unity) Thread::RunThreadWrapper
0x00007FF96EA226BD (KERNEL32) BaseThreadInitThunk
0x00007FF96FEAA9F8 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========

Editor hard-crashes when baking Scenes with LightBaker

Unity: Progressive Lightmapper

Fixed

Repro:

Note:

Observed:

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Editor hard-crashes when baking Scenes with LightBaker

Unity: Progressive Lightmapper

Statuses

Fixed

Resolution Notes

2023.2.XFixedResolved with this PR: https://github.cds.internal.unity3d.com/unity/unity/pull/25580

2023.1.XFixedResolved with this PR: https://github.cds.internal.unity3d.com/unity/unity/pull/25839

Description

Repro:

Note:

Observed:

Prioritise and Follow this issue

Have a workaround or additional info about this issue?