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
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
- MeshCollider preview gizmo disappears from the Scene view when overriding the mesh asset using any 3D editing tool
- Tutorial project is not created when started from the Get set up tab
- Audio Listener Component expands when selected
- [iOS] Frame Debugger rendering output doesn't work with iOS builds
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.