From: Chuck Lever <chuck.lever@oracle.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: brauner@kernel.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
linux-fsdevel@vger.kernel.org, chromium-dev@chromium.org
Subject: Re: 6.14/regression/bisected - commit b9b588f22a0c somehow broke HW acceleration in the Google Chrome
Date: Thu, 13 Feb 2025 10:39:35 -0500 [thread overview]
Message-ID: <3540acb6-0fe0-4c90-906b-def22aeffade@oracle.com> (raw)
In-Reply-To: <CABXGCsP9vPxu=hN5CO5MPJ5QVNJURKsBbbeb-NLoq60=M=CN3Q@mail.gmail.com>
On 2/13/25 10:27 AM, Mikhail Gavrilov wrote:
> On Thu, Feb 13, 2025 at 7:18 PM Chuck Lever <chuck.lever@oracle.com> 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
prev parent reply other threads:[~2025-02-13 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 2:16 6.14/regression/bisected - commit b9b588f22a0c somehow broke HW acceleration in the Google Chrome Mikhail Gavrilov
2025-02-13 14:17 ` Chuck Lever
2025-02-13 15:27 ` Mikhail Gavrilov
2025-02-13 15:39 ` Chuck Lever [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3540acb6-0fe0-4c90-906b-def22aeffade@oracle.com \
--to=chuck.lever@oracle.com \
--cc=brauner@kernel.org \
--cc=chromium-dev@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).