Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.12f1
Issue ID
UUM-59677
Regression
No
[Linux] Crash on d_cv_qualifiers when trying to build the Player with custom arguments
Reproduction steps:
1. Open the attached “CrashRepro” project
2. Open “Scripts/Editor/Builder.cs” Script
3. Set the build path in line 12
4. Close the project
5. Open the “Terminal” application
6. Execute this command: {{/Unity/Hub/Editor/2022.3.12f1/Editor$ ./Unity -quit -batchmode -nographics -projectPath "[path to project]" -executeMethod Builder.BuildWebGL -logFile "[path for log]/bapbap.log"}}
7. Observe the “Terminal” application
Expected result: The Player builds
Actual result: The Player build process crashes
Reproducible with: 2022.3.12f1
Reproducible on: Ubuntu 22.04, Ubuntu 20.04 (reported)
Not reproducible on: No other environment tested
First lines of the stack trace:
#0 0x0055e1c7952dec in burst_signal_handler(int, siginfo_t, void)
#1 0x007f3fca5a9420 in funlockfile
#2 0x0055e1ca7341db in d_cv_qualifiers
#3 0x0055e1ca73474d in d_name
#4 0x0055e1ca7339a2 in d_type
#5 0x0055e1ca733ba0 in d_type
#6 0x0055e1ca73412b in d_parmlist
Note: This issue does not reproduce all the time. One Ubuntu 22.04 machine was not able to reproduce the issue, while the other was able to, but with a different crash stack trace.
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, the possibility that future plans may solve the problem in a different way, that a workaround for the bug may be available, and the development team is unable to reproduce this issue for further investigation.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.