Search Issue Tracker

Won't Fix

Votes

0

Found in

2020.3.40f1

2021.3.11f1

2022.1.20f1

2022.2.0b10

2023.1.0a14

2023.2.0a1

Issue ID

UUM-16889

Regression

No

Editor crashes when a large array of doubles is initialized

--

-

Reproduction steps:

1. Create new or open any project
2. Attach “NewBehaviourScript.cs” to any GameObject in the scene
3. Enter the Play mode

Expected result: Editor doesn’t crash
Actual result: Editor crashes

Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.20f1, 2022.2.0b10, 2023.1.0a14

Reproduced on: Windows 10

First lines of the stack trace:
0x00007ff7c50c07d0 (Unity) CachedReader::Read
0x00007ff7c53b0616 (Unity) StreamedBinaryRead::Transfer<dynamic_array<double,0> >
0x00007ff7c53e1c70 (Unity) Transfer_Blittable_ArrayField<StreamedBinaryRead,double>
0x00007ff7c53c7220 (Unity) TransferField_LinearCollection<SafeBinaryRead>

Note: A large array of doubles usually means 50millions+ entries, couldn’t determine the exact array size to crash the editor consistently. Sometimes the editor will crash on recompiling the script containing a large array, for example when editing the script. If the issue is not reproducible, enter the Play mode until the Editor crashes
Note2: Unity currently only supports array < 2GB.

  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.

Comments (2)

  1. SimBoi

    Nov 22, 2023 09:35

    definitely not uncommon

  2. jhughes2112

    Oct 16, 2023 21:48

    Letting you know that this happens on a simple table of System.Numerics.Vector3[32768] as well. It isn't as uncommon as you might think to want a table of data in memory. I get a stack overflow whenever I access that table and it kills the Editor to the desktop.

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.