Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.2.0b2
2023.2.0a1
2023.3.0a3
Issue ID
UUM-7961
Regression
No
[Linux] Crash on burst_signal_handler when drawing lines using the Handles.DrawLines function
Reproduction steps:
1. Download and open the attached project: "Zeta.zip"
2. Go to Project window > Resources > Prefabs > Route > "Route" Prefab Asset
3. Add a new Waypoint in the Inspector window and edit one of its coordinates
Sample stack trace:
#0 0x0055faaea3cb3c in burst_signal_handler(int, siginfo_t, void)
#1 0x007f7de2eb6980 in funlockfile
#2 0x007f7c9a1df07b in _nv047glcore
#3 0x007f7c9a0fca77 in _nv016glcore
#4 0x007f7c9a1027f7 in _nv016glcore
#5 0x007f7c99d2699a in _nv026glcore
#6 0x007f7c99d26bbc in _nv026glcore
#7 0x0055faaefccbcc in DataBufferGLES::Upload(unsigned long, unsigned long, void const)
#8 0x0055faaefdbd8e in BufferGLES::EndWrite(unsigned long)
#9 0x0055faaefdbc25 in GfxDeviceGLES::EndBufferWrite(GfxBuffer, unsigned long)
Reproducible with: 2021.3.8f1, 2022.1.14f1, 2022.2.0b5, 2023.1.0a6
Could not test wish: 2020.338f1 (due to errors when opening the project)
Notes:
- Reproduced on Ubuntu 18.04
- The crash is not reproducible on Widows, an error is thrown instead: "IndexOutOfRangeException: Index was outside the bounds of the array."
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
We checked this issue internally and found that this would no longer repo and is not an issue since the timeframe from when this bug was filed vs current Ubuntu versions are different.
Dev mentioned that the bug is not repo'ing on all branch's.
Resolution Note (2023.3.X):
We checked this issue internally and found that this would no longer repo and is not an issue since the timeframe from when this bug was filed vs current Ubuntu versions are different.
Dev mentioned that the bug is not repo'ing on all branch's.