Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.5.X
Votes
1
Found in
2022.3.62f1
6000.0.54f1
6000.1.14f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113871
Regression
No
Editor crashes with prompt "The file 'MemoryStream' is corrupted! Remove it and launch unity again! [Position out of bounds!]" when adding a serialized field to a precompiled DLL
Reproduction steps:
1. Open the attached project "ReproProj"
2. In the menu bar, select “Crash > Test”
3. Repeat step 2
Expected result: Editor continues to run
Actual result: Editor crashes with prompt “The file 'MemoryStream' is corrupted! Remove it and launch unity again! [Position out of bounds!]“
Reproducible with: 2022.3.62f1, 6000.0.54f1, 6000.1.14f1, 6000.2.0f1, 6000.3.0a4
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Errors "UnityException: set_displayIndex is not allowed to be called during serialization" and "UnityException: Repaint is not allowed to be called during serialization" are present in the Editor.log
- No Stacktrace is present in the Editor.log
- The bug reporter is not present after the crash
- Reproducible with Mono and IL2CPP
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.