https://bugs.kde.org/show_bug.cgi?id=494083
Bug ID: 494083
Summary: kwin_wayland freezes or crashes while browsing
windy.com in Chrome
Classification: Plasma
Product: kwin
Version: 6.1.90
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: scene-opengl
Assignee: kwin-bugs-n...@kde.org
Reporter: ber...@codewiz.org
Target Milestone: ---
Related Chrome bug: https://issues.chromium.org/issues/371247946
NOTE: The root cause might very well be a mesa or Intel DRM bug. Reporting it
here because it seems kwin_wayland recovery code for GPU hangs is also failing
in some cases.
SUMMARY
The windy.com website often causes a GPU lockup which freezes the display for a
few seconds. Afterwards, kwin puts up a notification that effects have been
disabled.
On some occasions, kwin_wayland also crashes:
Oct 04 10:35:35 giskard kwin_wayland[1501]: kf.windowsystem: static bool
KX11Extras::mapViewport() may only be used on X11
Oct 04 10:35:35 giskard kwin_wayland[1501]: kwin_scene_opengl: 0x3:
GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1)
Oct 04 10:35:35 giskard kwin_wayland[1501]: kwin_scene_opengl: Invalid
framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Oct 04 10:35:35 giskard kwin_wayland[1501]: kwin_scene_opengl: 0x3:
GL_INVALID_OPERATION in glBindFramebuffer(non-gen name)
Oct 04 10:35:35 giskard kwin_wayland[1501]: kwin_scene_opengl: 0x3:
GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
STEPS TO REPRODUCE
Probably requires an Intel GPU to trigger.
1. Go to https://windy.com
2. Switch to the "Radar+" view
3. Zoom in and out or pan for a few seconds
IMPORTANT NOTES
- I can't find any other WebGL site reproducing this.
- This crash has been present for several months, so also with Plasma 6.1 and
with earlier versions of Chrome and Mesa.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.90
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Mesa: 24.2.3
--
You are receiving this mail because:
You are watching all bug changes.
