Search Issue Tracker

Won't Fix

Votes

0

Found in

2022.3.10f1

Issue ID

UUM-49613

Regression

Yes

[Entities Graphics] The Player or Editor crashes on "ConvertUTF16toUTF8" when running a complex Scene with Occlusion Culling

-

Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/LegacySampleScenes/OcclusionCulling/StressOcclusionCulling.unity” Scene
3. Build and Run
4. In Player press the button with the text “Next“

Expected result: The Player continues to run
Actual result: The Player crashes

Reproducible with: 1.0.14 (2022.3.10f1), 1.0.16 (2022.3.10f1)
Not reproducible with: 1.0.11 (2022.3.10f1)

Testing environment: Windows 10 Enterprise 21H2

Reproducible on:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Editor Play Mode

Not reproducible on: Windows Standalone Player

First few lines of Stacktrace:
0x00007ff740d35014 (Unity) ConvertUTF16toUTF8
0x00007ff7412a4d20 (Unity) UTF16String::GetScriptingString
0x00007ff741f3e216 (Unity) TooltipManager::Update
0x00007ff7420d7001 (Unity) Application::TickTimer
0x00007ff74254e16a (Unity) MainMessageLoop

Note:
- ENABLE_UNITY_OCCLUSION is added to the *Scripting Define Symbols*

  1. Resolution Note:

    Following the announcement here (https://forum.unity.com/threads/dots-development-status-and-next-milestones-november-2023.1516672/) we are removing experimental Burst Occlusion Culling feature.

    Today this case will be closed. Thank you for taking the time to report this issue.

Add comment

Log in to post comment