Search Issue Tracker

Won't Fix

Votes

0

Found in

2022.3.57f1

Issue ID

UUM-97029

Regression

No

Crash on BucketAllocator::Allocate when importing TextMeshPro assets

-

Reproduction steps:
1. Open the attached "repro_IN-94643" project
2. Open the "Assets/Scenes/TestingScene.unity" Scene
3. Observe the crash

Reproducible with: 2022.3.57f1
Not reproducible with: 6000.0.37f1, 6000.1.0b5, 6000.2.0a3
Fixed in: 2023.2.0a14

Reproducible on: Windows 10 (22H2)
Not reproducible on: No other environments tested

First few lines of the stack trace:
0x00007FF6775C018C (Unity) BucketAllocator::Allocate
0x00007FF6775B6A9E (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007FF6775A86C1 (Unity) MemoryManager::Allocate
0x00007FF6775B2B6E (Unity) malloc_internal
0x00007FF67770A110 (Unity) core::vector_detail::vector_data::grow

  1. Resolution Note:

    Thank you for submitting the bug report and providing the repro project.

    We were able to reproduce the crash in the provided project. The issue is caused by an invalid font asset that contains a 1x1 texture, which leads to memory corruption and eventually the crash in BucketAllocator::Allocate.

    In newer Unity versions, TextMesh Pro includes safeguards to prevent this scenario from causing a crash.

    To resolve the issue:
    - Please upgrade to a newer version of Unity, or
    - If you prefer to remain on Unity 2022.3, upgrade TextMesh Pro to version 3.2.0-pre.x.

    After upgrading, make sure to reimport the TextMesh Pro Essential Resources, as the shaders have been updated in the newer package.

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.