Open Bug 1801331 Opened 4 months ago Updated 4 months ago

Firefox uses much memory and many computes > black screen|crashes

Categories

(Core :: Performance, defect)

Firefox 107
defect

Tracking

()

UNCONFIRMED

People

(Reporter: iappstore, Unassigned, NeedInfo)

Details

Attachments

(1 file)

Attached file memory-report.json.gz

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

Opened many windows and tabs and let FF run for hours or several days.

Actual results:

FF uses much memory and many computes and fills up disk space (low disk error received from W10). Many times, seemingly as a result, the screen goes black and the system freezes for 30 sec or more. Sometimes it comes back, sometimes it hands. Sometimes BSOD.

Expected results:

None of the actual results should have occurred.

The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Performance
Product: Firefox → Core

Hi and thanks for opening this bug!
To be able to help you, could you please fill in the following information?

Basic information

Steps to Reproduce:

Expected Results:

Actual Results:


Performance recording (profile)

Profile URL:
(If this report is about slow performance or high CPU usage, please capture a performance profile by following the instructions at https://profiler.firefox.com/. Then upload the profile and insert the link here.)

System configuration:

OS version:
GPU model:
Number of cores:
Amount of memory (RAM):

More information

Please consider attaching the following information after filing this bug, if relevant:

  • Screenshot / screen recording
  • Anonymized about:memory dump, for issues with memory usage
  • Troubleshooting information: Go to about:support, click "Copy text to clipboard", paste it to a file, save it, and attach the file here.

Thanks so much for your help.

Flags: needinfo?(iappstore)
You need to log in before you can comment on or make changes to this bug.