Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2018.1.0b2
Issue ID
989625
Regression
No
ExecutableAndDlls is not found when checking through a PackedMemorySnapshot
The user's code goes over all snapshot.nativeObjects and checks if any nativeObject is greater than 300 MB to identify the ExecutableAndDlls entry. However, no object can be found.
Steps to reproduce:
1. Open user's attached project
2. Open scene "test"
3. Play the scene, open profiler, add memory profiler
4. Switch from "Simple" to "Detailed" view
5. Press "Take Sample: Editor" and expand "Other", notice the System.ExecutableAndDlls take more than 300MB
6. At the top of the editor press BugReport -> Open TestCode Window
7. Press "Capture Memory 'Editor' and observe there is nothing found
Expected result: Information about allocated ExecutableAndDlls is included in a PackedMemorySnapshot
Actual result: ExecutableAndDll is found as a nativeObject which is greater than 300MB
Reproduced with: 5.6.5p1, 2017.1.3f1, 2017.2.1p2, 2017.3.0p3, 2018.1.0b4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector loses focus or Material doesn't update when using GetModifiedMaterial with a Mask component
- Crash on GfxDeviceClient::AllocateBufferInternal when entering Play mode using Graphics.RenderPrimitives and Graphics.DrawProcedural in the scene
- Import TextMesh Pro window opens when the Text Mesh Pro Essentials and Examples are already imported when creating a new TextMesh Pro GameObject in the Hierarchy with TextMesh Pro settings reset
- Video is not rendered when the VideoPlayer GameObject is disabled and re-enabled after playback starts while using Material Override render mode
- Selection outline is not shown when selecting a high intensity HDR Swatch preset in Color Picker
Add comment