Search Issue Tracker

Fixed

Fixed in 2022.3.13f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12

Votes

3

Found in

2022.3.9f1

2023.1.12f1

2023.2.0b8

2023.3.0a4

Issue ID

UUM-48054

Regression

Yes

Crash on GetTargetAssemblyByScriptPath when a .po file in the Packages directory is not under an assembly definition

--

-

Reproduction steps:
1. Open the "IN-53218.zip" project

Expected results: The project opens successfully
Actual results: The Editor crashes

Reproducible with: 2022.2.0a8, 2022.3.9f1, 2023.1.12f1, 2023.2.0b8, 2023.3.0a4
Not reproducible with: 2021.3.30f1, 2022.2.0a7

Reproducible on: macOS 13.4 (M1, Intel), Windows 10
Not reproducible on: No other environment tested

First few lines of the stack trace:
#0 0x00000105da6738 in GetTargetAssemblyByScriptPath(core::basic_string<char, core::StringStorageDefault<char>> const&) #1 0x0000010642cd80 in GetGroupNameFromGUID(UnityGUID const&)
#2 0x0000010642cbe8 in LocalizationDatabase::ReloadAllEditorLocalizationAssets()
#3 0x000001042cb22c in CallbackArray::Invoke()
#4 0x00000105a30604 in ProfilerCallbackInvoke<CallbackArray, &GlobalCallbacks::editorFinishedLoadingProject>::Invoke(char const*)

Notes:
- Adding a "test.asmdef" file in the "Packages/test" directory fixes the issue
- Might also crash with 0 stack frames

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.