Bug 1828587 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch VMMap64.exe and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens.
- In the windows, click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens.
- In the windows, click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens.
- In the windows, click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
- Share the screenshot here.
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens.
- Share the screenshot here.
- In the windows, click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens.
- Share the screenshot here.
- In the VMMap window, click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens.
- Share the screenshot here.
- Ideally, if you can also click `File`, `Save As` to save the data then share that file with me at yjuglaret@mozilla.com, that is even better.
- In the VMMap window, click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens and share the screenshot here.
- Ideally, if you can also click `File`, `Save As` to save the data then share that file with me at yjuglaret@mozilla.com, that is even better.
- In the VMMap window, click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens and share the screenshot here.
- Ideally, if you can also click `File`, `Save As` to save the data then share that file with me at yjuglaret@mozilla.com, that is even better.
- In the VMMap window, if you click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens and share the screenshot here.
- Ideally, if you can also click `File`, `Save As` to save the data, then share that file with me at yjuglaret@mozilla.com, that is even better.
- In the VMMap window, if you click `Tools`, `Empty Working Set`, does this temporarily solve the issue?
Hello, thank you for your report! Can you try the following steps:
- Download [VMMap](https://learn.microsoft.com/en-us/sysinternals/downloads/vmmap).
- Reproduce the issue.
- Navigate to `about:processes` and identify the process ID for the GPU process, it should show as `GPU (XXXX)` where `XXXX` is the process ID.
- Launch `VMMap64.exe` and select the Firefox GPU process by process ID.
- Capture a screenshot of the VMMap window that opens and share the screenshot here.
- Ideally, if you can also click `File`, `Save As` to save the data into a file, then share that file with me at yjuglaret@mozilla.com, that is even better.
- In the VMMap window, if you click `Tools`, `Empty Working Set`, does this temporarily solve the issue?

Back to Bug 1828587 Comment 6