Search Issue Tracker

Fixed in 2021.2.X

Votes

6

Found in

2019.4

2020.3

2020.3.5f1

2021.2

Issue ID

1332514

Regression

No

Crash on MemoryManager::OutOfMemoryError when opening a project with corrupted .meta files

Serialization

-

Reproduction steps:
1. Open the attached "case_1332514" project
-- observe crash

Reproducible with: 2019.3.0f6, 2019.4.26f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a17
Not reproducible with: 2018.4.35f1

Errors right before the crash:
Could not allocate memory: System out of memory!
Cancelling DisplayDialog because it was run from a thread that is not the main thread: Fatal Error! Could not allocate memory: System out of memory!

A snippet from the stacktrace:
0x00007FF76ED1AC89 (Unity) MemoryManager::OutOfMemoryError
0x00007FF76ED14C38 (Unity) MemoryManager::Allocate
0x00007FF76ED1496C (Unity) MemoryManager::Allocate
0x00007FF76ED1496C (Unity) MemoryManager::Allocate
0x00007FF76ED1B6D2 (Unity) MemoryManager::ReallocateFallbackToAllocateDeallocate
0x00007FF76ED1B381 (Unity) MemoryManager::Reallocate
0x00007FF76ED29F08 (Unity) realloc_internal
0x00007FF76E451384 (Unity) dynamic_array_detail::dynamic_array_data::reallocate
0x00007FF76F8C3232 (Unity) dynamic_array_detail::dynamic_array_data::grow
0x00007FF771271F3C (Unity) UnityYAML::CompactNodeList::AddScalar
0x00007FF771256D6B (Unity) UnityYAML::Read::ParsePlainScalar
0x00007FF7712564FA (Unity) UnityYAML::Read::ParseNode
0x00007FF771255F31 (Unity) UnityYAML::Read::ParseInlineSequence

  1. Response avatar

    Resolution Note (fix version 2021.2):

    Out of memory crash, caused by specific sequence of characters in a corrupt .meta file. Error handing is fixed to avoid the crash, an error will be logged instead.

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.