Search Issue Tracker

Fixed

Votes

0

Found in

2022.3.17f1

2023.2.7f1

2023.3.0b4

6000.0.0b11

Issue ID

UUM-60930

Regression

Yes

Crash on multiple stack traces when opening a specific project

-

Reproduction steps:
1. Open the attached "project_IN-64929" project
2. Observe the crash

Reproduced with: 2022.2.0a15, 2022.3.17f1, 2023.2.7f1, 2023.3.0b4
Not reproduced with: 2021.3.34f1, 2022.2.0a14

Reproduced on: Windows 11 (10.0.22631) (user's), Windows 10 (22H2)
Not reproduced on: No other environments tested

Notes:

  • On 2022.3.17f1, when the “Safe Mode“ warning appears, press either “Enter Safe Mode“ or “Ignore“
  • When opening the project on 2022.2.0a15, it crashes before reaching the “Safe Mode“ warning
  • After downgrading to 2021.3.34f1-2022.2.0a14, then upgrading to 2022.2.0a15-2023.3.0b4 causes the project to not crash anymore

First few lines of the stack traces:
0x00007ff68d949355 (Unity) MatchAsset
0x00007ff68d948fba (Unity) MatchAsset
0x00007ff68d9344e8 (Unity) CategorizeAssets
0x00007ff68d913800 (Unity) RefreshInternalV2
0x00007ff68d91b7ff (Unity) StopAssetImportingV2Internal

0x00007FFC07E9CF1C (Unity) UpgradeStep_No_Script_Import
0x00007FFC07EA4B9F (Unity) <lambda_405664be159a40d980d50d0c1699cd69>::operator()
0x00007FFC07F2D067 (Unity) LMDB_Transaction::Run
0x00007FFC07EB29B6 (Unity) DatabaseUpgrader::UpgradeDatabase
0x00007FFC07E77C1E (Unity) DBVersionUpgrade

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.