Re: 6.14/regression/bisected - commit b9b588f22a0c somehow broke HW acceleration in the Google Chrome
63 views
Skip to first unread message
Mikhail Gavrilov
Feb 13, 2025, 10:29:42 AMFeb 13
to Chuck Lever, bra...@kernel.org, Linux List Kernel Mailing, Linux regressions mailing list, linux-...@vger.kernel.org, chromi...@chromium.org
On Thu, Feb 13, 2025 at 7:18 PM Chuck Lever <chuck...@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.
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.
--
Best Regards,
Mike Gavrilov.
> 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.
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.
--
Best Regards,
Mike Gavrilov.
Reply all
Reply to author
Forward
0 new messages