Closed Bug 1475826 Opened 8 years ago Closed 8 years ago

WebGL game laggy on latest Firefox (was fine before) while works perfectly on Chrome

Categories

(Core :: Graphics: CanvasWebGL, defect)

61 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox61 --- wontfix
firefox62 --- fixed
firefox63 --- fixed

People

(Reporter: shahin.dohan, Unassigned)

References

()

Details

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

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180704003137 Steps to reproduce: Started playing a WebGL game called "Rush Team", accessible from the following URL: https://www.asr-games.net/index.php?page=gameWebGL Actual results: The game in general seems to be very choppy and laggy. When I move the mouse, it takes a while for the move to happen in-game and in general all the movements are choppy as if I'm running the game on a very weak GPU even though I have a GTX 1080. Expected results: It should work as it did in earlier versions of Firefox, I last tried atleast maybe 3 months ago and none of these issues were present. I thought it was the game developers fault, but when I played the game on Chrome, everything was silky smooth.
(In reply to Shahin Dohan from comment #0) > It should work as it did in earlier versions of Firefox, I last tried > atleast maybe 3 months ago and none of these issues were present. It would be helpful if you could find the exact regression range. https://mozilla.github.io/mozregression/quickstart.html
Has Regression Range: --- → no
Component: Untriaged → Canvas: WebGL
Product: Firefox → Core
This issue does not occur in Firefox 60.1.0 Esr(2018-06-21)(64-bit) Firefox Beta 62.0b(2018-07-13)(64-bit) or Firefox Nighty 63.0a1 (2018-07-16)(64-bit) on Windows 10 Pro or Ubuntu 16.04 but it does occur in Firefox 61... Taken the above in consideration, we've run mozregression with --find-fix in order to find the fix that fixed this behavior. Unfortunately, the results are inconsistent, 4 mozregression runs, 4 different results, which do not seem to have anything in common with the nature of the bug. Maybe it would be interesting to find the bug-fix that resolved this issue, but given that the bug doesn't reproduce in Beta & Nightly, I'm updating the status flags and removing the regression-range request.
(In reply to Peter from comment #2) > Maybe it would be interesting to find the bug-fix that resolved this issue, > but given that the bug doesn't reproduce in Beta & Nightly, I'm updating the > status flags and removing the regression-range request. Thank you. You actually only set status-firefox61: affected. Considering the release version only receives security and stability patches, that should be wontfix. Since ESR, beta and nightly aren't affected, there's nothing left to do here.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [DUPEME]
Thank you guys! Sorry for not being active in my own thread, I was on vacation abroad. I'll wait for the fix in the next version of Firefox :)
You need to log in before you can comment on or make changes to this bug.