Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.2.0a1
2017.2.0f3
Issue ID
1025415
Regression
Yes
[Memory] 1 MB increase in RuntimeInitialize() memory due to TempBackgroundJobAlloc
Reproduction steps:
1. Open the attached project "EmptyProject";
2. Build the iOS project and open it through XCode;
3. Hold down the play button in XCode and select Profiling;
4. Open the Allocations tool and record.
Expected results: function start->main->RuntimeInitialize() should use the same amount of bytes in all versions.
Actual results: starting from 2017.2, the exact same functions uses 1MB more memory than in the 2017.1.
Reproduced on: 2017.2.0a1, 2017.2.2p3, 2017.3.2f1, 2017.4.1f1, 2018.1.0f1. 2018.2.0b1.
Not reproduced: 2017.1.3p3.
Reproduced on device: Iphone 6 Plus (10.3.2).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Add comment