Search Issue Tracker

Won't Fix

Won't Fix in 6000.4.X

Votes

0

Found in

6000.0.60f1

6000.3.1f1

6000.4.0a5

Issue ID

UUM-130801

Regression

No

Crash on memset when calling RuntimeContentManager.LoadLocalCatalogData()

Core Runtime

-

Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/_repro_stuff/LOADER_SCENE.unity” Scene
3. Enter the Play Mode
4. Observe the crash

Reproducible with: 1.4.2 (6000.0.60f1, 6000.3.1f1), 6.4.0 (6000.4.0a5)
Not reproducible with: 1.4.3 (6000.3.1f1), 6.5.0 (6000.5.0a3)

Reproducible on: Windows 11
Not reproducible on: No other environment tested

First few lines of the stack trace:
0x00007FF9E4154470 (Unity) memset
0x00007FF9E0747679 (Unity) UnsafeUtility_CUSTOM_MemSet 0x0000021DC1C9B8E6 (Mono JIT Code) (wrapper managed-to-native) Unity.Collections.LowLevel.Unsafe.UnsafeUtility:MemSet (void,byte,long)
0x0000021DC20E0B1B (Mono JIT Code).\Library\PackageCache\com.unity.collections@aea9d3bd5e19\Unity.Collections\UnsafeHashMap.cs:71] Unity.Collections.LowLevel.Unsafe.HashMapHelper1<Unity.Entities.Serialization.UntypedWeakReferenceId>:Clear ()
0x0000021E85CC4AFB (Mono JIT Code)[.\\Library\\PackageCache\\com.unity.collections@aea9d3bd5e19\\Unity.Collections\\UnsafeHashMap.cs:161] Unity.Collections.LowLevel.Unsafe.HashMapHelper1<Unity.Entities.Serialization.UntypedWeakReferenceId>:ResizeExact (int,int)

Note:

In 1.4.3 and 6.5.0 entities versions, “ArgumentException: Capacity 1869373812 value too large. Maximum capacity is 536870912.” error is thrown, when entering the Play Mode

  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.

  2. Resolution Note (6000.4.X):

    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.