Search Issue Tracker
Fixed in 0.2.6
Votes
0
Found in [Package]
0.2.5-preview.1
Issue ID
1271886
Regression
No
[Memory Profiler] Snapshot can be imported again even when it's already added in the Snapshot list
How to reproduce:
1. Create a new project
2. Import the Memory Profiler from the Package Manager
3. Open the Memory Profiler window (Window -> Analysis -> Memory Profile)
4. Make a Snapshot by clicking the 'Capture Editor' button
5. Click the 'Import' button and select the newly taken Snapshot located in the MemoryCaptures folder
Expected result: the same Snapshot is not imported twice and a warning message occurs
Actual result: the same Snapshot is allowed to be imported
Reproducible with: 0.1.0-preview.1 (2018.4.26f1), 0.2.5-preview.1 (2019.4.9f1, 2020.1.3f1, 2020.2.0a21)
Notes:
When one of the imported Snapshots gets deleted from the list and the other one is opened, 'Could not find file' and 'NullReferenceException: Object reference not set to an instance of an object' exceptions get logged in the Console
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
Add comment