Repository navigation
Exported memory data should go to the ~/Downloads folder #3411
Description
Users are having a difficult time finding the memory exports after exporting. We should export the file to the ~/Downloads directory like we do for the performance and cpu profiler pages so we have a consistent export experience.
Activity
bkonyi commentedon May 5, 2022
There's also no way to import a heap snapshot for comparison, which could be useful.
snipd-mikel commentedon Jan 19, 2023
Is there a way to find the file that is currently exported? I couldn't find it anywhere.
polina-c commentedon Jan 27, 2023
In current version this feature is buggy. In details:
Do you really need export? In current version export on memory screen does not store any information beyond chart. If you want to save information on tabs, use button 'CSV'. You will not be able to reopen it though.
Export on memory screen, if DevTools runs in Chrome or VSCode, does not store the file. So, if you want to store it, use the steps, replacing
-d chromewith-d macosto run macos version and record the video to catch popup with file name.Screen.Recording.2023-01-27.at.8.12.24.AM.mov
kenzieschmoll commentedon Jan 27, 2023
@polina-c I'd recommend that we disable the export feature for now until it is fully supported. Otherwise we are providing a broken experience. Issue: #5045
kenzieschmoll commentedon Apr 29, 2026
This issue is likely obsolete due to the memory screen rewrite. Modern browsers handle download locations natively, typically defaulting to the Downloads folder. If there is more work to do here, please let us know by filing a new issue with up to date information. Thanks!