Closed Bug 1871207 Opened 2 years ago Closed 2 years ago

Offscreen canvas testcase from bug 1870488 will quickly eat up all RAM on Windows (GPU-canvas), cause computer crash and generate gfx-logs

Categories

(Core :: Graphics: Canvas2D, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1870488
Tracking Status
firefox-esr115 --- unaffected
firefox121 --- unaffected
firefox122 --- unaffected
firefox123 --- fix-optional

People

(Reporter: mayankleoboy1, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Use latest Nightly
Set the following :
gfx.direct2d.disabled = true
gfx.canvas.accelerated = true
gfx.canvas.remote.worker-threads = 0

Open the testcase from bug 1870488 (https://bugzilla.mozilla.org/attachment.cgi?id=9369102)

AR:

  1. The VRAM quickly starts increasing (The process level RAM doesnt increase, but the total system-level RAM increases)
  2. The GPU use is very low (pre-regression ,it was 50%)
  3. Rapid fluctuation in process-level RAM (250MB-700MB)
    After a while, my computer would freeze

Regression range:

Bug 1829026 - Handle KERN_ABORTED from semaphore_wait. r=aosmond

semaphore_wait and semaphore_timedwait can return KERN_ABORTED, much
like POSIX semaphores can return EINTR, and need to restart their
waits for correct behavior.

Differential Revision: https://phabricator.services.mozilla.com/D195952

Edit : These STR/regression range are for GPU-canvas only. For D2D-canvas, I filed bug 1871208 for easier tracking.

See Also: → 1871208
Summary: Testcase from Bug 1870488 will quickly eat up all the RAM on Windows and causes errors ing gfx-log → Offscreen canvas testcase from bug 1870488 will quickly eat up all RAM on Windows (GPU-canvas), cause computer crash and generate gfx-logs
Attached file about:support

Set release status flags based on info from the regressing bug 1829026

:lsalzman, since you are the author of the regressor, bug 1829026, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Since this expression of the bug is in a not-enabled-by-default config, this is not that alarming right now. It also seems like this pre-existed bug 1829026, and this is just about a new interaction with that.

Severity: -- → S4
Flags: needinfo?(lsalzman)
Priority: -- → P5

Lee, the Severity seems low on this one for the number of affected users. Should we bump it up?

Flags: needinfo?(lsalzman)

It's fine. This is not a default config.

Flags: needinfo?(lsalzman)
Severity: S4 → S3
No longer blocks: 1870488
Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1870488
Resolution: --- → DUPLICATE
See Also: 1871208
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: