Open Bug 1453265 Opened 7 years ago Updated 2 years ago

performance regression in WebGL

Categories

(Core :: Graphics, defect, P3)

60 Branch
x86_64
Windows 10
defect

Tracking

()

Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- wontfix
firefox59 --- unaffected
firefox60 --- wontfix
firefox61 --- wontfix
firefox62 --- fix-optional

People

(Reporter: alice0775, Unassigned)

References

()

Details

(Keywords: parity-chrome, perf, regression, Whiteboard: [gfx-noted])

Attachments

(1 file)

version : fps -------------------- 52.7.3ESR : 160-180 53.0.3 : 160-180 54.0.2 : 160-180 55.0.2 : 90-110 56.0.2 : 100-130 57.0.4 : 100-130 58.0.2 : 110-130 59.0.2 : 100-130 60.0b11 : 65-95 61.0a1 : 65-95 Chrome Dev67: 230-245 Regression window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=d9f8ec82354d03faa5e0475004ffb8cc31bad8d6&tochange=8ee92682ad1f3b67c110742bc910cf1af03ac48b Regressed by: Bug 1440849
Keywords: parity-chrome
Attached file about:support (deleted) —
Flags: needinfo?(jgilbert)
Priority: -- → P3
Whiteboard: [gfx-noted]
Flags: needinfo?(jgilbert)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: