Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.1.2p4
Issue ID
1001733
Regression
No
[macOS] [.NET 3.5] Relatively slow concurrent managed allocations
Reproduction steps:
1. Open the attached project.
2. Play the 'main' scene.
3. Check notifications in the Console tab.
Actual result:
macOS .NET 3.5:
Operations took 193 ms warming up
Operations took 221 ms on main thread
Operations took 161 ms on non-main thread
Operations took 5436 ms in thread pool
macOS .NET 4.6:
Operations took 111 ms warming up
Operations took 172 ms on main thread
Operations took 95 ms on non-main thread
Operations took 161 ms in thread pool
Windows .NET 3.5:
Operations took 175 ms warming up
Operations took 174 ms on main thread
Operations took 170 ms on non-main thread
Operations took 321 ms in thread pool
Expected result:
- There is most likely room for optimization. (Operations took 5436 ms in thread pool)
Reproduced with:
macOS (.NET 3.5)
5.5.6f1, 5.6.5p2, 2017.1.3p1, 2017.2.1p4, 2017.3.1p1, 2018.1.0b7
Not reproducible with:
macOS (.NET 4.6)
Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
Add comment