Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67727 - [chromium] Address hint field will glitch when started maximized

Attached to Project: Arch Linux
Opened by Gnattu OC (gnattu) - Wednesday, 26 August 2020, 20:00 GMT
Last edited by Evangelos Foutras (foutrelis) - Friday, 09 October 2020, 20:55 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

When chromium 85.0.4183.83-1 is started as a maximized window, the address hint field will have a glitched corner(see attached gif). The glitch does not appear if vulkan is enabled, or manually resize(restore and re-maximize) the window after launch. I cannot reproduce this on 84.0.4147.135-1. I cannot reproduce this on other disto(ubuntu and fedora) using the google-chrome official release either.

Additional info:
* package version(s)
chromium 85.0.4183.83-1
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.3-arch1-1
RX 470 with amdgpu on Mesa 20.1.6

* config and/or log files etc.
not so helpful:
[21015:21015:0826/144830.870745:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

* link to upstream bug report, if any

Steps to reproduce:

- Install chromium 85.0.4183.83-1
- launch it, if it does not start as maximized, maximize it then quit, then launch it again.
- Type in the address bar, the glitch appears.
- Resize the window then maximize the window again, the glitch no longer appears.


   Peek 2020-08-26 14-33.gif (74.7 KiB)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Friday, 09 October 2020, 20:55 GMT
Reason for closing:  Fixed
Additional comments about closing:  chromium 86.0.4240.75-1
Comment by Mehmet (mmt84) - Thursday, 27 August 2020, 12:59 GMT
I've the same problem with a RX 5700 on KDE 5.19.4. All my packages are up-to-date as of now.

Mesa 20.1.6
Linux 5.8.3
Chromium 85.0.4183.83

Also this doesn't work for me: "Resize the window then maximize the window again, the glitch no longer appears."
Comment by Gnattu OC (gnattu) - Thursday, 27 August 2020, 13:42 GMT
For me, chromium will behave normal for some time, and I have to resize the window when the glitch appears again. With extensive repeating, I could get some cases that resizing does not fix the glitch as well.
Comment by Evangelos Foutras (foutrelis) - Thursday, 27 August 2020, 18:09 GMT
Similar upstream report: https://crbug.com/1122224
Comment by Mika Attila (solvedsnake) - Wednesday, 09 September 2020, 13:21 GMT
I don't know if there are any significant drawbacks to this, but I enabled the vulkan backend in chrome://flags, and it doesn't have these glitches, and I haven't noticed any other glitches or noticeable performance decrease with it.
I'm using an RX 580. This might be a good workaround for people with modern AMD graphics hardware until this bug is fixed.

EDIT: One drawback seems to be that pepper flash content doesn't seem to render at all, but since it's EOL anyway, it's probably not a deal breaker for most people.
Comment by Evangelos Foutras (foutrelis) - Friday, 09 October 2020, 17:46 GMT
https://crbug.com/1122224 is marked as fixed for Chromium 86. Can you confirm it's resolved?
Comment by Mehmet (mmt84) - Friday, 09 October 2020, 20:20 GMT
I can confirm that the issue is resolved.

Loading...