Search Issue Tracker

Won't Fix

Votes

0

Found in

2022.3.17f1

Issue ID

UUM-60081

Regression

Yes

Crash on core::StringStorageDefault<char>::assign when selecting "Quit" in the "Fatal Error!" pop-up after opening a project

-

Reproduction steps:
1. Open the attached “repro-project“
2. In the “Enter Safe Mode?“ pop-up select “Ignore“
3. Observe the project opening with a “Fatal Error!“ pop-up
4. In the pop-up select “Quit“
5. Observe the crash

Reproducible with: 2022.3.6f1, 2022.3.17f1
Not reproducible with: 2021.3.34f1, 2022.3.5f1, 2023.1.0a1, 2023.2.5f1, 2023.3.0b2

Reproduced on: Windows 10
Not reproducible on: No other environment tested

Notes:
1. The Editor does not crash in Safe Mode
2. The “Fatal Error!“ pop-up displays a memory allocation error message, indicating a system out of memory condition (“{{Could not allocate memory: System out of memory! Trying to allocate: 1976818346745B with 16 alignment. MemoryLabel: TempOverflow Allocation happened at: Line:525 in C:\build\output\unity\unity\Runtime\Core\Containers\StringStorageDefault.h Memory overview}}“)

First few lines of the stack traces:
0x00007ff7b4c820fb (Unity) core::StringStorageDefault<char>::assign
0x00007ff7b6ee97b6 (Unity) GUIDPersistentManagerV2::PathIDToFileIdentifierInternal
0x00007ff7b6ee95fe (Unity) GUIDPersistentManagerV2::OnRegisterAssetType
0x00007ff7b5b28a43 (Unity) PersistentManager::MakeObjectsPersistent
0x00007ff7b5b284e1 (Unity) PersistentManager::MakeObjectPersistentAtFileID

0x00007FF8D1DACF19 (KERNELBASE) RaiseException
0x00007FF7EA7CA7DE (Unity) LaunchBugReporter
0x00007FF7EA196BBB (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF7EA19749D (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF7EAE4948F (Unity) DebugStringToFilePostprocessedStacktrace

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

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.