Re: 6.14/regression/bisected - commit b9b588f22a0c somehow broke HW acceleration in the Google Chrome

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/13/25 10:27 AM, Mikhail Gavrilov wrote:
> On Thu, Feb 13, 2025 at 7:18 PM Chuck Lever <chuck.lever@xxxxxxxxxx> wrote:
>> I need a simpler reproducer, please. "Chrome stopped working" doesn't
>> give me anything actionable.
>>
> 
> After applying commit b9b588f22a0c, the internal page chrome://gpu/ in
> Google Chrome indicates that GPU acceleration is no longer functional.

The connection between tmpfs and GPU acceleration is ... mysterious ;-)


> I apologize, but as I am not a Google Chrome engineer, I have no idea
> how to create more clean reproducer code.
> I only noticed as a Web browser user that when I scrolled through
> pages with a lot of images, Google Chrome got substantially sluggish.
> Hopefully, someone from chromium-dev will read my message and help us.

Understood. Maybe a better place to start would be for you to file a bug
against Chrome/Chromium, report the same information that you reported
here, and let them dig into it first. I'll still be here waiting for
details... if their issue tracker permits, add me to the Cc list of the
bug report.


-- 
Chuck Lever




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux