Search Issue Tracker
Fixed in 0.8.0-preview.8
Votes
2
Found in [Package]
0.6.0-preview.7
Issue ID
1313547
Regression
No
Writing bytes to the driver when packet's size is 1386/1387/1388 fails and Unity crashes
Reproduction steps:
1. Open the user's attached project and Scenes/SampleScene scene
2. In the Hierarchy window, select Server GameObject
3. In the Inspector window, disable PadPacketsOfBadLength
4. Enter the Play mode
Expected result: Writing bytes to the driver when packet's size is 1386, 1387 or 1388 succeeds and Unity doesn't crash
Actual result: Writing bytes to the driver when packet's size is 1386, 1387 or 1388 fails and Unity crashes
Reproducible with: (0.6.0-preview.7) 2020.2.4f1, 2021.1.0b7, 2021.2.0a5
Could not test with: 2018.4.32f1 (Unity Transport is not available), 2019.4.20f1 (could not downgrade Unity Transport package)
Notes:
1. Errors from the Editor.log:
"Error whilst writing bytes to driver (size=1386) - see below exception.",
"System.InvalidOperationException: System.NullReferenceException: Object reference not set to an instance of an object
This Exception was thrown from a function compiled with Burst, which has limited exception support.
Stacktrace truncated - please add `Debug = true` to BurstCompile.
0x00007ff6eb1caffd (Unity) burst_signal_handler
0x00007ff9f64a83dc (ntdll) RtlDeleteAce
0x00007ff9f647b406 (ntdll) RtlRaiseException
0x00007ff9f64cfe3e (ntdll) KiUserExceptionDispatcher
0x00007ff9ab1a12b0 (a54e8b170e4c6a40f23838b19e1d51b) burst.initialize0"
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 0.8.0-preview.8):
Fixed in Unity Transport 0.8.0-preview.8