Effect causes micro-freeze/extended lag when enabled [KDE Neon].

[InkstainTheBat]

After enabling the effect, about every 30s or so, the desktop would freeze for a few seconds. Inputs would be registered and everything resumes as expected once the freeze is done. All I could find were some repeated entries in journalctl:

gen 09 16:01:24 simone-KDEN kwin_wayland[1693]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
gen 09 16:01:24 simone-KDEN kwin_wayland[1693]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
gen 09 16:01:24 simone-KDEN kwin_wayland[1693]: kwin_better_blur: Failed to create an offscreen framebuffer

However, nothing appeared during the freezes themselves.

[taj-ny]

X11 or Wayland?
Which KDE Neon edition are you using?
Is there an application this issue can be reliably reproduced with?

[InkstainTheBat]

Wayland. I haven't verified what happens on X11 yet. I've noticed there's a slightly higher chance of it happening when anything translucent (including the panel and app launcher) appears on screen. This is made worse by the fact the Kvantum theme I'm using (Layan) renders nearly every qt app translucent in some way

[taj-ny]

Which KDE Neon edition are you using?

You didn't answer this question. Also, are you using v1.3.4 or main?

[InkstainTheBat]

Sorry, I wasn't home and couldn't check. I'm using version 1.3.4 (latest I assume) and this is the info on the "About This System"

KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-49-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i5-14400F
Memory: 31,2 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2
Manufacturer: ASUS```
Hopefully this also contains any other information you may need

[taj-ny]

Try the issue-160 branch, the Failed to create an offscreen framebuffer message should now contain some additional information, paste it here.

[InkstainTheBat]

I thought I had sent another reply explaining what happened but it seems I didn't.
The issue appears to have resolved itself. I am still on the issue-160 branch, and although the only changes made seem to be more debug messages, no freezes occur nor errors relating to this in journalctl. If I had to hazard a guess it'd be that something went wrong with my previous compilation of 1.2.4.

[forkiesassds]

I have been happening a similar issue with this. As it turns out, when checking with the issue-160 branch, the XWayland screenshare bridge is causing my journal to be flooded with this if I do anything on my secondary monitor.

saus. 23 19:06:19 localhost kwin_wayland[53022]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
saus. 23 19:06:19 localhost kwin_wayland[53022]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
saus. 23 19:06:19 localhost kwin_wayland[53022]: kwin_better_blur: Failed to create an offscreen framebuffer "xwaylandvideobridge xwaylandvideobridge" QRectF(0,672 1x1) QRectF(-99,573 100x100) QPointF(0,672) QRegion(0,0 1x1) QRegion(0,672 1x1) QRect(0,672 1x1) QRect(0,672 1x1)

[taj-ny]

Does adding xwaylandvideobridge to the window class list solve it? I assume you're using the Blur all except matching setting.

[forkiesassds]

Yes, adding it to the excludes list ended up fixing the problem. I guess there should be a check if a window has valid dimensions, although it could also be included to the excludes list by default.