zoomrmc Reporter
	Description • 7 years ago

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171013042429

Steps to reproduce:

Automatic upgrade to v56.


Actual results:

Whole experience became frustratingly laggy. Scrolling is choppy, new tabs open with a lag.
Safe mode, Refreshing, new profile, turning e10 off/on with browser.tabs.remote.autostart don't affect the issue. Switched to beta with no results.

Issue affect the machine with W7 and an ancient GPU, which is probably the one to blame. However, earlier versions (pre-56) worked smoothly.

	Kohei Yoshino [:kohei]
	Comment 1 • 7 years ago

Please make sure you have up-to-date graphics drivers: https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

	beldirai
	Comment 2 • 7 years ago

This is also happening on my end, with up-to-date graphics drivers. FF 57 works quite smoothly when opening the browser, but after hours of browsing begins to experience lag spikes. This lag happens on every single site, though the ones most affected are audio sites (like sound effect databases) and video sites (like Youtube).

1. Whenever I open my browser for the day, every site works fast and looks normal. After 5-6 hours of browsing, every new tab I open ends up lagging and shows up as a blank page with a barely visible loading icon. It stays that way for like 30sec-1min and then slowly loads the page. The pages look like this. https://imgur.com/a/5puza

2. Youtube also works fine for a while after opening the browser. However, 5-6 hours later, it suddenly goes haywire and all videos load into a black screen. The audio can always be heard, but the video itself won't show up until you pause it. https://imgur.com/a/hi95k It's not caused by hardware acceleration since I disabled that years ago, and disabling WebGL does nothing to fix the issue.

3. This is also happening to any audio site I use. When I try to listen to any audio file, be it free sound effects or folk music MIDIs, the file either begins to play, or doesn't. It depends on the amount of time I've been using my browser. If the site has been open for hours, the file will begin to lag - the music skips if it's already playing, and doesn't start if it isn't. The only way to make the file play is to refresh the entire site.

Here are my about:support and about:memory reports to make things easier. (I have a feeling this happens to more than just one user so it might be a performance bug.)
http://textuploader.com/d4x81
https://justpaste.it/1cg42

	Andrew McCreight [:mccr8]
	Comment 3 • 7 years ago

(In reply to zoomrmc from comment #0)
> Issue affect the machine with W7 and an ancient GPU, which is probably the
> one to blame. However, earlier versions (pre-56) worked smoothly.

I don't know if that preference still works to disable e10s. Maybe it isn't actually disabling e10s? We have some known issues with lower end machines getting bad issues. You could look in about:support and see if "Web Content Processes" has a non-zero value.

	Andrew McCreight [:mccr8]
	Comment 4 • 7 years ago

(In reply to beldirai from comment #2)
> This is also happening on my end, with up-to-date graphics drivers. FF 57
> works quite smoothly when opening the browser, but after hours of browsing
> begins to experience lag spikes. This lag happens on every single site,
> though the ones most affected are audio sites (like sound effect databases)
> and video sites (like Youtube).

This sounds like a memory leak, which is probably different than the initial bug. Please file a new bug in bugzilla and CC me on it. If you get a memory report in that case, please save it using "measure and save" and attach it to the bug, instead of copy and pasting it because that's hard to read. Thanks!

	Ben Kelly [:bkelly, not reviewing]
	Comment 5 • 7 years ago

In regards to comment 0, to disable e10s you need to set this slightly different pref to false:

 "browser.tabs.remote.autostart.2"

Note, the .2 at the end.

	Ben Kelly [:bkelly, not reviewing]
	Comment 6 • 7 years ago

Can you try again with e10s disabled as described in comment 5?  I'm worried this is more related to thread starvation we've seen in some other e10s conditions.

	Selena Deckelmann :selenamarie :selena
	Comment 7 • 7 years ago

Closing INCOMPLETE. Please re-open if you're able to provide the information requested in comment 5.

	beldirai
	Comment 8 • 6 years ago

The issue with the unplaying files and black video screen have been fixed for me, so I have a feeling there's no need for a bug report anymore. 

...The lag is still happening, but it's less pronounced than before. I've already gotten used to having to kill the browser a few times every week to stop it from freezing. Sometimes the lag causes a peculiar issue where the top half of a website has loaded, but the bottom half is white for around 10-30 seconds before it loads - this only happens when the browser has been open for hours and has already started to slow down. Here's an example of what it looks like: https://imgur.com/a/Fx51ChB I'm not sure if this is a bug, or even worth reporting, or whether you already know about it, but I thought I'd share it anyway.

Let me know if you want me to post an actual bug report of that, I'll try to see what I can do. (I suck at posting bugs, though. I'm not very good at digging deeper, despite being tech-savvy.)