Search Issue Tracker
Third Party Issue
Third Party Issue in 2023.1.X
Votes
0
Found in
2019.4.40f1
2020.3.37f1
2021.3.7f1
2022.2.0b3
2023.1.0a4
Issue ID
UUM-9853
Regression
No
Multi-threaded operations take longer when in non-Windows builds
How to reproduce:
1. Open the user's attached project
2. Build and Run the project for macOS or Linux (File -> Build and Run)
3. After the build launches, navigate to the build folder
4. Open the "time.txt" file and observe the time logged after "Single apply tooh"
Expected result: wait time of 25000ms or under is logged
Actual result: wait time of 100000ms or more is logged
Reproducible with: 2019.4.40f1, 2020.3.37f1, 2021.3.7f1, 2022.2.0b3, 2023.1.0a4
Reproducible on: macOS 11.6, Ubuntu 20.04
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
- WebGPU errors when CoreCopy shader is used to copy an MSAA texture
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
Resolution Note:
The code taking time seem to be the native code compiled in libtzergity_native. This is not Unity code.
The user should investigate how this library is built (check optimization options, multithreading support etc.)
Resolution Note (2023.1.X):
The code taking time seem to be the native code compiled in libtzergity_native. This is not Unity code.
The user should investigate how this library is built (check optimization options, multithreading support etc.)