Closed
Bug 1439664
Opened 6 years ago
Closed 6 years ago
Firefox nightly with webrender enabled has graphical glitches
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: beingalink, Unassigned)
References
Details
(Keywords: nightly-community)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180220103456 Steps to reproduce: Login to my Nextcloud and open the menu. See screenshot attached. Actual results: The menu isn't rendered completely. (A few days ago nightly also crashed or freezed but that doesn't seem to happen anymore.) Expected results: The menu should be rendered completely.
Reporter | ||
Updated•6 years ago
|
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
Comment 1•6 years ago
|
||
Nightly 60 x64 20180220220044 de_DE @ Debian Testing (KDE, Radeon RX480) Can't reproduce on Linux. :/ My Nextcloud menu looks fine, but it has a different order.
Updated•6 years ago
|
Blocks: stage-wr-trains
Priority: -- → P2
Reporter | ||
Comment 2•6 years ago
|
||
Not sure if realted but scrolling on https://www.prosieben.de makes current nightly with webrender enabled freeze here. As I already said, I'm on MacOS 10.13.3, Macbook Pro 13.3" late 2016.
Comment 3•6 years ago
|
||
(In reply to beingalink from comment #2) > Not sure if realted but scrolling on https://www.prosieben.de makes current nightly with webrender enabled freeze here. That sounds like bug 1439921.
Reporter | ||
Comment 4•6 years ago
|
||
Scrolling my twitter timeline works fine though.
Reporter | ||
Comment 5•6 years ago
|
||
The same glitch is present under windows 10, too.
Comment 6•6 years ago
|
||
(In reply to beingalink from comment #0) > The menu isn't rendered completely. (A few days ago nightly also crashed or freezed but that doesn't seem to happen anymore.) Was it always visually broken like this or is this a regression?
OS: Mac OS X → All
Reporter | ||
Comment 7•6 years ago
|
||
(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #6) > (In reply to beingalink from comment #0) > > The menu isn't rendered completely. (A few days ago nightly also crashed or freezed but that doesn't seem to happen anymore.) > > Was it always visually broken like this or is this a regression? It's fine with webrender disabled and it used to be fine with webrender, too iirc.
Comment 8•6 years ago
|
||
(In reply to beingalink from comment #2) > As I already said, I'm on MacOS 10.13.3, Macbook Pro 13.3" late 2016. Could you try to find a regression range? https://mozilla.github.io/mozregression/install.html mozregression --good 2018-01-12 --bad 2018-02-20 --pref gfx.webrender.all:true
Reporter | ||
Comment 9•6 years ago
|
||
Unfortunately I can't install mozregression as it doesn't work with python3 and the system provided python 2.7 seems to have issues: Installing collected packages: six, mozprofile, mozdevice, mozrunner, idna, pycparser, cffi, enum34, asn1crypto, ipaddress, cryptography, pyOpenSSL, requests, mozinstall, mohawk, slugid, taskcluster, colorama, configobj, mozregression, blessings Found existing installation: six 1.4.1 DEPRECATION: Uninstalling a distutils installed project (six) has been deprecated and will be removed in a future version. This is due to the fact that uninstalling a distutils project will only partially uninstall the project. Uninstalling six-1.4.1: Exception: Traceback (most recent call last): File "/Library/Python/2.7/site-packages/pip-9.0.1-py2.7.egg/pip/basecommand.py", line 215, in main status = self.run(options, args) File "/Library/Python/2.7/site-packages/pip-9.0.1-py2.7.egg/pip/commands/install.py", line 342, in run prefix=options.prefix_path, File "/Library/Python/2.7/site-packages/pip-9.0.1-py2.7.egg/pip/req/req_set.py", line 778, in install requirement.uninstall(auto_confirm=True) File "/Library/Python/2.7/site-packages/pip-9.0.1-py2.7.egg/pip/req/req_install.py", line 754, in uninstall paths_to_remove.remove(auto_confirm) File "/Library/Python/2.7/site-packages/pip-9.0.1-py2.7.egg/pip/req/req_uninstall.py", line 115, in remove renames(path, new_path) File "/Library/Python/2.7/site-packages/pip-9.0.1-py2.7.egg/pip/utils/__init__.py", line 267, in renames shutil.move(old, new) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 302, in move copy2(src, real_dst) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", line 103, in copystat os.chflags(dst, st.st_flags) OSError: [Errno 1] Operation not permitted: '/tmp/pip-QofvLp-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/six-1.4.1-py2.7.egg-info'
Reporter | ||
Comment 10•6 years ago
|
||
Another rendering glitch, not sure if related to the first one (all icons should be in a circle). Generally the ui rendering of add-on windows when clicking on their icons is also very slow (time to appearance) in current nightly with webrender enabled on macOS.
Reporter | ||
Comment 11•6 years ago
|
||
Also on Twitter the round avatars "flash in squares".
Reporter | ||
Comment 12•6 years ago
|
||
The original rendering issue on Nextcloud seems to be fixed in current nightly. The "flashing in square" of the round avatars on twitter is still happening though. Also the slow reaction off add-on buttons is still there with webrender enabled. Not sure if related though.
Comment 13•6 years ago
|
||
(In reply to beingalink from comment #12) > The original rendering issue on Nextcloud seems to be fixed in current nightly. > The "flashing in square" of the round avatars on twitter is still happening though. If this is still happening, please file a separate bug about it and attach about:support as text file. Thank you.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Comment 14•6 years ago
|
||
(In reply to beingalink from comment #12) > The "flashing in square" of the round avatars on twitter is still happening though. That might have been bug 1423087.
You need to log in
before you can comment on or make changes to this bug.
Description
•