Search Issue Tracker

Active

Under Consideration for 6000.5.X

Votes

0

Found in

6000.0.68f1

6000.3.2f1

6000.4.0b9

6000.5.0a7

Issue ID

UUM-134462

Regression

No

Crash with multiple stack traces when baking a specific Navmesh Surface

AI Navigation Core

-

How to reproduce:
1. Open the attached “IN-130259” project
2. Open the “Eldara” scene
3. In the Hierarchy, search for “nav“
4. Click on the “NavMesh Surface” GameObject
5. In the Inspector, click “Bake”
6. Wait for ~5 minutes
7. Observe the crash

Reproducible with: 2.0.5 (6000.0.38f1), 2.0.10 (6000.0.0b13, 6000.0.68f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7)
Could not test with: 6000.0.0b12 (could not bake the NavMesh Surface)

Reproduced on: Windows 11
Not reproduced on: No other environment tested

First few lines of the stack trace:
0x00007FF9CC00DA7D (Unity) DynamicHeapAllocator::CreateTLSFBlock
0x00007FF9CC00C4B5 (Unity) DynamicHeapAllocator::Allocate
0x00007FF9CC00BA3D (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007FF9CC00CA3D (Unity) MemoryManager::Allocate

or:
0x00007FFA86FA1C07 (Unity) core::base_hash_set<core::pair<core::basic_string<char,core::StringStorageDefault<char> > const ,keywords::GlobalKeyword,1>,core::hash_pair<core::hash<core::basic_string_ref<char> >,core::basic_string<char,core::StringStorageDefault<char> > >,core::equal_pair<std::equal_to<core::basic_string_ref<char> >,core::basic_string<char,core::StringStorageDefault<char> > > >::lookup<core::basic_string_ref<char>,core::equal_pair<std::equal_to<core::basic_string_ref<char> >,core::basic_string<char,core::StringStorageDefault<char> > > >
0x00007FFA86FA841E (Unity) keywords::KeywordRemap::Init
0x00007FFA86FCEFA2 (Unity) ShaderLab::IntShader::CreateKeywordRemap
0x00007FFA86FD1C9C (Unity) ShaderLab::IntShader::ResolveFallback

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.