Windows only: Are able to reproduce the issue with [this custom build](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ILBTUeO1RruRxJwHqBp9cA/runs/0/artifacts/public/build/install/sea/target.installer.exe)? If yes, please navigate to `about:memory` while the memory is still high, and click `Measure`. That should create a `report.txt` file on your Desktop. If you could then share that file here as an attachment, that should help us diagnose this issue. Thank you! Note: This is custom behavior that is specific to this custom build. I am not asking for the contents of `about:memory`. The `report.txt` will contain specific information that is relevant for the investigation.
Bug 1828587 Comment 31 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Windows only: Are able to reproduce the issue with [this custom build](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ILBTUeO1RruRxJwHqBp9cA/runs/0/artifacts/public/build/install/sea/target.installer.exe)? If yes, please navigate to `about:memory` while the memory is still high, and click `Measure`. That should create a `report.txt` file on your Desktop. If you could then share that file here as an attachment, that should help us diagnose this issue. Thank you! Note: This is custom behavior that is specific to this custom build. I am not asking for the contents of `about:memory`. The `report.txt` file will contain specific information that is relevant for the investigation.
~~Windows only: Are able to reproduce the issue with [this custom build](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ILBTUeO1RruRxJwHqBp9cA/runs/0/artifacts/public/build/install/sea/target.installer.exe)? If yes, please navigate to `about:memory` while the memory is still high, and click `Measure`. That should create a `report.txt` file on your Desktop. If you could then share that file here as an attachment, that should help us diagnose this issue. Thank you!~~ Note: This is custom behavior that is specific to this custom build. I am not asking for the contents of `about:memory`. The `report.txt` file will contain specific information that is relevant for the investigation. Edit: No more required thanks to comment 45.
Edit: No more required thanks to comment 45. Windows only: Are able to reproduce the issue with [this custom build](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ILBTUeO1RruRxJwHqBp9cA/runs/0/artifacts/public/build/install/sea/target.installer.exe)? If yes, please navigate to `about:memory` while the memory is still high, and click `Measure`. That should create a `report.txt` file on your Desktop. If you could then share that file here as an attachment, that should help us diagnose this issue. Thank you! Note: This is custom behavior that is specific to this custom build. I am not asking for the contents of `about:memory`. The `report.txt` file will contain specific information that is relevant for the investigation.