Closed
Bug 1460981
Opened 6 years ago
Closed 6 years ago
multiple redraws make Firefox unusably slow under X Windows
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1263222
People
(Reporter: kdo, Unassigned)
Details
(Keywords: perf)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180509235650 Steps to reproduce: Firefox is essentially unusable over X Windows. It is extremely slow and uses all the bandwidth of a 100Mb network. To make a simple test, I created a new profile "empty" with default settings, and ran "firefox -P empty about:blank" on Ubuntu 16.04 with DISPLAY set to another machine on which I had allowed direct network connections to the X server. On the machine running Firefox I ran wireshark to watch all packets being sent over this connection. It sent 27MB of data, mostly drawing on the screen. Naturally this takes several seconds to send. The window is 1280 x 1040 x 24 bits, and thus contains 4MB of data. So to display the blank window it has written more than 6 times the amount of data stored in the bitmap. Doing anything more complicated, even displaying a simple page with some basic HTML, will use even larger amounts of data. This may be related to bug 299727 but in that case the reporter said he had to to various things to get slow behavior, whereas here even the simplest test produces the problem.
Comment 1•6 years ago
|
||
:smaug it would be appreciated if you could look into this, or at least sort it where it belongs.
Severity: normal → critical
Flags: needinfo?(bugs)
Keywords: perf
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Updated•6 years ago
|
Component: Untriaged → Widget: Gtk
Flags: needinfo?(bugs)
Product: Firefox → Core
Comment 2•6 years ago
|
||
Let's start from widget, but this might be more like a graphics bug.
Flags: needinfo?(karlt)
Comment 3•6 years ago
|
||
I expect this is the same issue as bug 1263222.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(karlt)
Resolution: --- → DUPLICATE
As suggested in bug 1263222, I set gfx.xrender.enabled, and that decreased the network usage in the test case above from around 30 MB to around 11 MB, which still seems kind of high, but it's much better than before.
You need to log in
before you can comment on or make changes to this bug.
Description
•