Search Issue Tracker

Fixed

Fixed in 6000.3.0b2, 6000.4.0a1

Votes

0

Found in

2022.3.66f1

6000.3.0a6

6000.4.0a1

Issue ID

UUM-115148

Regression

Yes

Crash on mono_custom_attrs_has_attr when opening a specific project

-

How to reproduce:
1. Open the attached “IN-112094“ project
2. Observe the crash

Reproducible with: 2022.1.0a10, 2022.3.66f1, 2023.1.0a9, 6000.3.0a5 (36d7e9fd6645), 6000.3.0a6
Not reproducible with: 6000.0.56f1, 6000.2.2f1, 6000.3.0a4
Fixed in: 2023.1.0a10

Reproducible on: MacOS 15.5 (M4), Windows 11 (by user)
Not reproducible on: No other environments tested

Note: The project has to be unzipped each time it is opened. The issue doesn't always reproduce consistently, especially when switching between different Unity versions.

First few lines of the stack trace:

{noformat}#0 0x0000017ea9c5b0 in mono_custom_attrs_has_attr
#1 0x00000101427384 in SerializableAttributeManager::DidDomainReload()
#2 0x000001007cfaa0 in CallbackArray::Invoke()
#3 0x0000010132921c in ProfilerCallbackInvoke<CallbackArray, &GlobalCallbacks::didReloadMonoDomain>::Invoke(char const*)
#4 0x00000101328250 in MonoManager::FinalizeReload()
#5 0x00000102b0cca4 in ScriptingInitializer::FinalizeReload()
#6 0x00000102bc36dc in RefreshInternalV2(AssetDatabase::UpdateAssetOptions, ScanFilter const&, InternalRefreshFlagsV2) {noformat}

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.