Search Issue Tracker
Not Reproducible
Not Reproducible in 1.8.X
Votes
0
Found in [Package]
1.8.12
Issue ID
BUR-2621
Regression
No
[Linux] Editor crashes when executing project build tests
How to reproduce:
- Open the attached project named "project-blobario-main"
- Open the Test Runner Window
- Switch to Edit mode tests
- Select and execute build tests
Expected result: The tests are executed without an editor crash
Actual results: Editor crashes during test execution
Reproducible with: 2022.3.19f1, 2023.3.0b5
Possible regression point - Burst 1.8.11 -> 1.8.12
Notes:
- Only reproduced on Linux (Ubuntu 20)
- Reproducible in batchmode as well as regular Editor
Comments (2)
-
thwachchayhngsxeiym37
Jan 29, 2024 19:03
ขอบคุณ
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:
Could not repeat with 1.8.12 or 1.8.16, and I can't see anything in the reproduction to indicate why burst would have an impact on this. It looks like a memory trample, if you have a solid reproduction, please try launching unity with --burst-disable-compilation on the command line. If it still reproduces, then its definitely not a burst issue. (because the issue is a memory stomp, any difference in memory layout could cause the bug to manifest)
If however it does not reproduce, please provide details on the specification of the machine being used. Core counts, memory etc.
Resolution Note (1.8.X):
Could not repeat with 1.8.12 or 1.8.16, and I can't see anything in the reproduction to indicate why burst would have an impact on this. It looks like a memory trample, if you have a solid reproduction, please try launching unity with --burst-disable-compilation on the command line. If it still reproduces, then its definitely not a burst issue. (because the issue is a memory stomp, any difference in memory layout could cause the bug to manifest)
If however it does not reproduce, please provide details on the specification of the machine being used. Core counts, memory etc.