Search Issue Tracker

Fixed in 6000.5.0b7

Fixed in 6000.6.0a4

Votes

0

Found in

6000.3.13f1

6000.4.3f1

6000.5.0b4

6000.6.0a3

Issue ID

UUM-139910

Regression

Yes

Crash on FindSeamTexels when generating lighting while the meshAtlasIndex >= 0

Lighting

-

How to reproduce:
1. Open the attached “IN-139325” project
2. Open the “Game” scene
3. Open the Lighting window (Window > Rendering > Lighting)
4. Click “Generate Lighting”
5. Observe the crash

Reproducible with: 6000.3.12f1, 6000.3.13f1, 6000.4.3f1, 6000.5.0b4, 6000.6.0a3
Not reproducible with: 6000.0.73f1, 6000.3.11f1

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Notes:
- Sometimes the crash can take up to 1 minute to occur after completing step 4
- An “Assertion failed on expression: 'meshAtlasIndex >= 0'“ error appears in the Console window before the crash occurs

First few lines of the stack trace:
0x00007FFC8EA98D24 (Unity) FindSeamTexels
0x00007FFC8EA9A259 (Unity) StitchSeams
0x00007FFC8EA9945C (Unity) SeamStitchingHelperStitchJob
0x00007FFC90784E28 (Unity) ujob_execute_job
0x00007FFC9078422F (Unity) lane_guts
0x00007FFC90787FA9 (Unity) worker_thread_routine

  1. Resolution Note (fix version 6000.5.0b7):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.

    We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.

    Thank you for helping us improve Unity!

  2. Resolution Note (fix version 6000.6.0a4):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.

    We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.

    Thank you for helping us improve Unity!

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.