New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 691624 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Description frame overlay shows garbage on the last line when the frame's height is different of the previous

Reported by alexandr...@gmail.com, Feb 13 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
There are many places where the bug can be seen and they all happen in the same way.

1. Open a few tabs and go to different sites where the page's title will be displayed with different height. Suggestions:
- 2 line description frame overlay: http://askubuntu.com/questions/737233/how-can-i-set-the-default-terminal-preferably-from-the-command-line
- 1 line description frame overlay: https://translate.google.com/

2. Let the mouse pointer rest over one of the tab, so the description/information frame overlay will appear.

3. On the first try, it may or may not show the problem.
3a. If the description looks fine, move the pointer to the other tab, so its description frame overlay appears.
3b. If the description frame overlay appears with garbage on the last line, move the pointer somewhere else to make it go. Then put the pointer back on the tab to make the description frame overlay appear once more (which should be fine now).

N.B. The same can be done over links (or other elements) containing a title. This should display a description/information frame overlay.

What is the expected behavior?
The content should be readable and complete every time.

What went wrong?
Most of the time, if the description frame overlay is of a different height than the previous one, no consideration to the element the description frame overlay is attached to, its content will be shifted up by one line, showing garbage on the last line. In other words, the problem could be seen by pointing first on a link or an image or a tab containing a "title", then to any other elements (link, image, tab...) containing a "title" or a "description" to be displayed in such a description frame overlay.

Moving the pointer away (to close the description) and back (make it appear once more) on the same element or on an element that uses a description frame of the same height fixes the problem, this time showing the text as expected (see attached picture, showing both the problematic display and the correct one side by side).

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: ArchLinux
Flash Version: Shockwave Flash 23.0 r0

Tested on at least two different configurations, both using ArchLinux 64bit.
- Configuration 1: using latest radeonsi driver stack all built from gits
- Configuration 2: using latest nouveau driver up until last week, now on radeonsi driver stack, both provided by the distribution

The problem has been there for as long as I can remember (more than a year at least) on the first configuration. The second configuration is newer, and the problem was seen using both an older 8400 GS (nouveau) and a newer R7 360 (radeonsi).

 
Missing attached picture
Description frame overlay bug.png
39.4 KB View Download

Comment 2 by ajha@chromium.org, Feb 14 2017

Labels: Needs-Triage-M56
Cc: rbasuvula@chromium.org
Labels: Needs-Feedback
Thanks for filing the issue.
Tested in chrome # 56.0.2924.87 and Canary #58.0.3019.0 on Ubuntu 14.04 and not able to reproduce the issue.Please find the screen cast for your reference.

@ alexandre.f.demers: Could you please let me know if i have missed anything and if possible, provide us with a URL of the issue which would help us to triage the issue further.

Thanks in Advance.
691624.ogv
1.8 MB View Download
Ok, so just in case, I reset all the flags that could have influenced the rendering. Now, I only have access to machines with Radeon GPUs anymore (R9 280X and R7 360). But it was the same with the NVidia GPU using Nouveau driver.

That being said, here is a recording I've done for you displaying the problem.
description-overlay-display-bug.mkv
1.1 MB Download
By the way, you'll notice that sometime the text seems to show a slight delay before showing the appropriate description in the overlay, as if there was a double refresh of its content. Otherwise, I suspect it would show the bug.
Labels: -Needs-Feedback
Thank you for providing feedback. removing "Needs-Feedback" label.
Cc: kavvaru@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on windows 7,Ubuntu 14.04 using chrome version 56.0.2924.87.Able see the content title description without any issues.
Please find the attached screen cast and confirm if anything missed here.

Request you please try the issue on new profile without any extensions/Flags and update the thread if the issue still persists.

Thanks,
691624.ogv
3.6 MB View Download
First, this is a Linux problem only, no need to try reproducing it under Windows.

Now, both of you rbasuvula and kavvaru are testing against Ubuntu 14.04. Can you tell me your mesa, drm, ddx and kernel versions? If you are using the latest default mesa drivers from Ubuntu 14.04, you must be running against mesa 10.1.3, which is a 3 year old version. Can't you test against a live image of Archlinux or Ubuntu or an updated version of Ubuntu?

On my side, it was tested and confirmed on three different setups, all using ArchLinux: one with an nvidia 8600GT (drivers from packages provided by the system, nouveau mesa driver), and two with AMD gpus, which are a R9 280X (display stack built from git repositories [drm, radeonsi mesa, ddx] with a radeon kernel-4.9 driver) and a R7 360 (drivers from packages provided by the distro [radeonsi mesa] and amdgpu kernel-4.9 driver).

Also, I can add that I'm running Gnome Shell on Wayland, but I've tested also with Gnome Shell on Xorg with the same result.

Tested also with different profiles, with and without extensions/flags.

Here is a digest about the setup running the R9 280X (I can provide a similar digest for the R7 360 setup):
[from glxinfo]
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD TAHITI (DRM 2.48.0 / 4.9.11-1-ARCH, LLVM 4.0.0) (0x6798)
    Version: 17.1.0
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD TAHITI (DRM 2.48.0 / 4.9.11-1-ARCH, LLVM 4.0.0)

[from Xorg.0.log]
[   161.818] (II) "glx" will be loaded by default.
[   161.818] (II) LoadModule: "dri3"
[   161.818] (II) Module "dri3" already built-in
[   161.818] (II) LoadModule: "glamoregl"
[   161.818] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[   161.827] (II) Module glamoregl: vendor="X.Org Foundation"
[   161.827] 	compiled for 1.19.2, module version = 1.0.0
[   161.827] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   161.827] (II) LoadModule: "glx"
[   161.827] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   161.843] (II) Module glx: vendor="X.Org Foundation"
[   161.843] 	compiled for 1.19.2, module version = 1.0.0
[   161.843] 	ABI class: X.Org Server Extension, version 10.0
[   161.843] (II) LoadModule: "radeon"
[   161.843] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[   161.857] (II) Module radeon: vendor="X.Org Foundation"
[   161.857] 	compiled for 1.19.1, module version = 7.8.99
[   161.857] 	Module class: X.Org Video Driver
[   161.857] 	ABI class: X.Org Video Driver, version 23.0
[   161.857] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
[...]
[   161.937] (II) [KMS] Kernel modesetting enabled.
[   161.937] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   161.937] (II) RADEON(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[   161.937] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[   161.937] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[   161.937] (==) RADEON(0): Default visual is TrueColor
[   161.937] (**) RADEON(0): Option "DRI" "3"
[   161.937] (**) RADEON(0): Option "TearFree" "on"
[   161.937] (==) RADEON(0): RGB weight 888
[   161.937] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[   161.937] (--) RADEON(0): Chipset: "TAHITI" (ChipID = 0x6798)
[   161.937] (II) Loading sub module "fb"
[   161.937] (II) LoadModule: "fb"
[   161.937] (II) Loading /usr/lib/xorg/modules/libfb.so
[   161.950] (II) Module fb: vendor="X.Org Foundation"
[   161.950] 	compiled for 1.19.2, module version = 1.0.0
[   161.950] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   161.950] (II) Loading sub module "dri2"
[   161.950] (II) LoadModule: "dri2"
[   161.950] (II) Module "dri2" already built-in
[   161.950] (II) Loading sub module "glamoregl"
[   161.950] (II) LoadModule: "glamoregl"
[   161.950] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[   161.950] (II) Module glamoregl: vendor="X.Org Foundation"
[   161.950] 	compiled for 1.19.2, module version = 1.0.0
[   161.950] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   161.950] (II) glamor: OpenGL accelerated X.org driver based.
[   162.602] (II) glamor: EGL version 1.4 (DRI2):
[   162.604] (II) RADEON(0): glamor detected, initialising EGL layer.
[   162.604] (II) RADEON(0): KMS Color Tiling: enabled
[   162.604] (II) RADEON(0): KMS Color Tiling 2D: enabled
[   162.604] (**) RADEON(0): TearFree property default: on
[   162.604] (II) RADEON(0): KMS Pageflipping: enabled
[   162.633] (II) RADEON(0): Output DisplayPort-0 has no monitor section
[   162.695] (II) RADEON(0): Output HDMI-0 has no monitor section
[   162.696] (II) RADEON(0): Output DVI-0 has no monitor section
[   162.710] (II) RADEON(0): Output DVI-1 has no monitor section
[   162.739] (II) RADEON(0): EDID for output DisplayPort-0
[   162.802] (II) RADEON(0): EDID for output HDMI-0
[...]
[   162.817] (II) Loading sub module "ramdac"
[   162.817] (II) LoadModule: "ramdac"
[   162.817] (II) Module "ramdac" already built-in
[   162.817] (--) Depth 24 pixmap format is 32 bpp
[   162.817] (II) RADEON(0): [DRI2] Setup complete
[   162.817] (II) RADEON(0): [DRI2]   DRI driver: radeonsi
[   162.817] (II) RADEON(0): [DRI2]   VDPAU driver: radeonsi
[   162.817] (II) RADEON(0): Front buffer size: 8640K
[   162.817] (II) RADEON(0): VRAM usage limit set to 2803327K
[   162.817] (II) RADEON(0): SYNC extension fences enabled
[   162.817] (II) RADEON(0): Present extension enabled
[   162.817] (**) RADEON(0): DRI3 enabled
[   162.817] (==) RADEON(0): Backing store enabled
[   162.817] (II) RADEON(0): Direct rendering enabled
[   162.917] (II) RADEON(0): Use GLAMOR acceleration.
[   162.917] (II) RADEON(0): Acceleration enabled
[   162.917] (==) RADEON(0): DPMS enabled
[   162.917] (==) RADEON(0): Silken mouse enabled
[   162.917] (II) RADEON(0): Set up textured video (glamor)
[   162.917] (II) RADEON(0): [XvMC] Associated with GLAMOR Textured Video.
[   162.917] (II) RADEON(0): [XvMC] Extension initialized.
[   162.917] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[...]

[from dmesg]
[    2.119772] [drm] Initialized
[    2.125156] [drm] radeon kernel modesetting enabled.
[    2.125789] checking generic (c0000000 7f0000) vs hw (c0000000 10000000)
[    2.125789] fb: switching to radeondrmfb from VESA VGA
[    2.125808] Console: switching to colour dummy device 80x25
[    2.126061] [drm] initializing kernel modesetting (TAHITI 0x1002:0x6798 0x174B:0x3001 0x00).
[    2.126069] [drm] register mmio base: 0xFEA00000
[    2.126069] [drm] register mmio size: 262144
[    2.126133] ATOM BIOS: Tahiti
[    2.126170] [drm] Changing default dispclk from 500Mhz to 600Mhz
[    2.126178] radeon 0000:01:00.0: VRAM: 3072M 0x0000000000000000 - 0x00000000BFFFFFFF (3072M used)
[    2.126179] radeon 0000:01:00.0: GTT: 2048M 0x00000000C0000000 - 0x000000013FFFFFFF
[    2.126181] [drm] Detected VRAM RAM=3072M, BAR=256M
[    2.126181] [drm] RAM width 384bits DDR
[    2.126223] [TTM] Zone  kernel: Available graphics memory: 8059794 kiB
[    2.126223] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    2.126224] [TTM] Initializing pool allocator
[    2.126228] [TTM] Initializing DMA pool allocator
[    2.126244] [drm] radeon: 3072M of VRAM memory ready
[    2.126244] [drm] radeon: 2048M of GTT memory ready.
[    2.126256] [drm] Loading tahiti Microcode
[    2.126338] [drm] Internal thermal controller with fan control
[    2.126384] [drm] probing gen 2 caps for device 1002:5a16 = 33ed02/0
[    2.131508] [drm] radeon: dpm initialized
[    2.132307] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[...]
[    4.433791] fbcon: radeondrmfb (fb0) is primary device
[    4.456465] Console: switching to colour frame buffer device 240x67
[    4.459409] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[    4.478280] [drm] Initialized radeon 2.48.0 20080528 for 0000:01:00.0 on minor 0




Project Member

Comment 9 by sheriffbot@chromium.org, Mar 8 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: TE-Hardware-Dependency
Project Member

Comment 11 by sheriffbot@chromium.org, Mar 9 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment