Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.7.1-preview.1
1.1.0
Issue ID
PROFB-238
Regression
No
Warning is thrown when capturing a Snapshot of an iOS Player
How to reproduce:
1. Open the attached Project "profilerTest.zip"
2. Build and Run a Development Build on iOS
3. Open the Memory Profiler Window (Window->Analysis->Memory Profiler)
4. Attach the Memory Profiler to the running Player
5. Capture a Snapshot
6. Inspect the Snapshot
Expected result: No warnings can be seen in the Snapshot
Actual result: The following warning is thrown:
"System Allocator is used. It is generally advised to use the Dynamic Heap Allocator instead.
Dynamic Heap Allocator is generally more efficient than the System Allocator. Additionally, Native Objects can be allocated outside of Native Regions when using the System Allocator."
Reproducible with: 0.7.1-preview.1 (2021.3.40f1), 1.1.0 (2022.3.36f1, 6000.0.9f1)
Reproduced on:
- iPad Pro (9.7 inch, WiFi) (iOS 14.8)
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
- Select Preset "None" icon changes after switching tabs
- [Android] Crash when using xxHash3 and targeting the ARMv7 Architecture with IL2CPP Scripting Backend
- GameObject reference in a Script Component becomes missing when unpacking a variant of another Prefab variant
- Project Settings vertical separator position is not synchronized with the mouse position when dragging it horizontally
- Crash on PhysicsDebugDraw::SelectFiltering::Update when entering play mode with Physics Debug window docked and unfocused
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.
We have addresses this specific customer's issue and let them know it does not occur when using matching and up-to-date versions.
Our ISS customers’ bug reports have a higher weight than normal, and this is accounted for in the decision. We hare happy to have worked with you to find a suitable workaround in the short term. Today, however, 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.