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
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
Add comment