X.Org X server

After upgrading to 16.10, Chrome has become unusable because of extremely slow update

Bug #1628866 reported by Urban Engberg on 2016-09-29

This bug affects 14 people

Affects		Status	Importance	Assigned to	Milestone
	X.Org X server	Invalid	Undecided	Unassigned
	xorg (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Both Chrome and Firefox actually were extremely slow regarding visual update (1 second after clicking a tab, lagging when entering text). Examining this old report: https://bugs.launchpad.net/ubuntu-gnome/+bug/1386721, I tried disbling bootloader graphics and VESA framebuffer, which suddenly made firefox behave as it used to, but chrome shows no improvement.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu Sep 29 12:19:56 2016
DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
InstallationDate: Installed on 2016-04-28 (153 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20BTS26N00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
dmi.bios.date: 03/12/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N14ET28W (1.06 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BTS26N00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BTS26N00
dmi.product.version: ThinkPad X1 Carbon 3rd
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Thu Sep 29 12:15:18 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

Tags:

Revision history for this message

Urban Engberg (uengberg) wrote on 2016-09-29:

BootLog.txt Edit (4.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (63.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.9 MiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (26.0 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (5.3 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (21.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.1 KiB, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (8.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (350 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (185.6 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (628 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (43.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (44.5 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (15.2 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (11.6 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (544 bytes, text/plain; charset="utf-8")
xserver.outputs.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2016-09-30:

Sounds like this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=85064

Revision history for this message

Urban Engberg (uengberg) wrote on 2016-09-30:

Starting chrome with LIBGL_DRI3_DISABLE=1 definitely seems to make a difference, it is now blazingly fast. Do you know if there is any general solution planned?

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2016-10-05:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1615871, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-01-18:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status:	New → Confirmed

Revision history for this message

Starbeamrainbowlabs (sbrl) wrote on 2017-02-25:

I've discovered that I'm affected by this bug, but *only* when I've got 2 chrome windows open on different desktops (I've got a 2x2 grid of desktops) on Ubuntu 16.10 - it wasn't doing this on Ubuntu 16.04.

How can this be a duplicate of a webkit bug when chrome doesn't even use webkit though?

uname -a: Linux Riikaan 4.8.0-39-generic #42-Ubuntu SMP Mon Feb 20 11:47:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

glxinfo:

name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Kabylake GT2 (0x5916)
    Version: 12.0.6
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Kabylake GT2
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.0.6
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 12.0.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

More information available on request.

Revision history for this message

bagl0312 (bagl0312) wrote on 2017-03-08:

I am experiencing the same problem with chrome version 56.0.2924.87 (64-bit)
and ubuntu 16.04 after the update to 16.04.2
chrome becames very slow in scrolling and loading pages when multiple chrome windows are opened in different workspaces.
I am also not sure that this is a duplicated bug, or just a different one

---------------------

uname -a: Linux nbbag7 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

glxinfo:

name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2) (0x191e)
    Version: 12.0.6
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2)
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.0.6
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 12.0.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

Revision history for this message

Erik van den Bergh (evdbergh) wrote on 2017-03-13:

Chiming in to say I experience the same thing, extreme slowdown and stuttering in chromium but only when a second window is open on a separate workspace.

uname -a: Linux Latitude-7480 4.8.0-41-generic #44-Ubuntu SMP Fri Mar 3 15:27:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

glxinfo:

name of display: :0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Kabylake GT2 (0x5916)
    Version: 12.0.6
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
*truncated*, more info available if needed

From the previous posts it seems that the Intel graphics are at fault perhaps?

Revision history for this message

Colan Schwartz (colan) wrote on 2017-04-18:

I removed the duplicate marker as I don't believe this to be a duplicate of bug #1615871 (Poor performance with WebKit on yakkety with Intel modesetting enabled).

The upstream bug is really https://bugs.chromium.org/p/chromium/issues/detail?id=683486 , but I can't find any way to add the remote watch. Can someone help?

Revision history for this message

T Martin (mortramalt) wrote on 2017-04-19:

#10

This bug began affecting me on April 16, 2017. I'm using Chrome 57 and when I move one window to my bottom 2x2 vertical desktop, the UI is extremely laggy. Moving it back to desktop 1 resolves the issue immediately.

$ uname -a
Linux eldritch 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Does not seem to affect Firefox.

Colan Schwartz (colan) on 2017-04-19

tags:

added: zesty

Revision history for this message

Szilárd Páll (sin-pecado) wrote on 2017-04-24:

#11

Given the claims on the upstream bug, this should perhaps be filed against compiz?

Revision history for this message

Victoid (djvictoid) wrote on 2017-05-14:

#12

Explicitly loading the intel driver in xorg.conf and enabling DRI3 appears to have worked around this issue in Chrome/Chromium, using intel's latest driver distribution.

[ 3026.999] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20160711
[ 3026.999] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 (Timo Aaltonen <email address hidden>)

Please see comment #31 in the chromium bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=683486#c31

Bug Watch Updater (bug-watch-updater) on 2017-10-06

Changed in xorg-server:
importance:	Unknown → High
status:	Unknown → Confirmed

Revision history for this message

dino99 (9d9) wrote on 2018-02-26:

#13

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

Changed in xorg (Ubuntu):
status:	Confirmed → Invalid
Changed in xorg-server:
importance:	High → Undecided
status:	Confirmed → New
status:	New → Invalid