Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.0a13
Issue ID
UUM-1693
Regression
No
Unity Crashes when using serializedObject.CopyFromSerializedPropertyIfDifferent() and the provided property is an ".Array.size"
How to reproduce:
1. Open the user attached project
2. Open the "SampleScene" scene
3. Select the "Example" GameObject
4. Press the "Copy" button that is in the Inspector
Reproducible with: 2019.4.0f1, 2019.4.39f1, 2020.3.34f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
First lines of stack trace:
0x00007FF82C314F69 (KERNELBASE) RaiseException
0x00007FF6562DB7FF (Unity) LaunchBugReporter
0x00007FF655D13352 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF655D141FC (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF656CFD527 (Unity) DebugStringToFilePostprocessedStacktrace
0x00007FF656CFCA88 (Unity) DebugStringToFile
0x00007FF6551C14DC (Unity) CachedReader::OutOfBoundsError
0x00007FF6551C2364 (Unity) CachedReader::UpdateReadCache
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
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.