SUMMARY When the translucency desktop effect is enabled, minimizing firefox causes it to freeze until it is un-minimized. STEPS TO REPRODUCE 1. Enable 'translucency' desktop effect 2. Minimize all firefox windows (a 'busy' firefox session is implied) 3. Application is unresponsive OBSERVED RESULT ``` Jul 03 15:17:04 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:28 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:30 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:33 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:34 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:36 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:37 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:38 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:40 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:42 Pallas kwin_wayland[10116]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined Jul 03 15:18:42 Pallas plasmashell[10446]: QUnifiedTimer::stopAnimationDriver: driver is not running Jul 03 15:18:42 Pallas plasmashell[10446]: kpipewire_logging: invalid image "EGL_BAD_PARAMETER" ``` Each of the 'TypeError' messages is generated when minimizing a firefox window. After the last messages appear together (stopAnimationDriver/ BAD_EGL_PARAMETER), video playback continues for a short time (maybe 1 minute?) but eventually stops. Restoring one of the browser windows from minimized during this time, the page initially appears OK, but any interaction has no result... Until all of the firefox windows are restored, and then all of the input that was sent to each of the windows simultaneously happens, and video playback continues (usually at extremely low quality until the page is reloaded) EXPECTED RESULT No freeze with translucency effect enabled SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Tumbleweed (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Sorry if this is filed in the wrong place, It's not entirely clear to me where bugs in desktop effects should be reported. Any advice appreciated.
> a 'busy' firefox session is implied What does this mean, exactly? Are you using the Wayland session, or the X11 session? Does it happen in a new clean user account using that same session type?
Hi Nate thanks for asking :) TLDR This is super racey and difficult to repro, sufficiently difficult that I thought I should mention the bug to help out the next person to hit it, and also probably impossible for you to repro so you can work on it. Totally fine with you closing this outright if you can't repro it. At least if someone gets stuck, they can find this if they search. (In reply to Nate Graham from comment #1) > > a 'busy' firefox session is implied > What does this mean, exactly? It means we can't make it do this with a clean FF session, it needs a bunch of windows to minimize, so that the last one of them will 'die'. I spent a few hours a couple weeks back, creating a fresh profile and fleshing it out with a few windows with several tabs, and was able to repro with that, so generally, I just used my real ff session. I can repro this and toggle it on and off like a switch, now that I know how, but at first it seemed completely intermittent and random. I had to get the thing into this state somehow, and I had to realise this pattern of behaviour (minimising windows) combined with the settings I changed (enabling desktop effects) was the 'trick'. It's very "race"y (I mean, it bears the marks of a race condition) in its behaviour, so I don't think this one will be an easy repro and I don't expect anyone to spend any kind of time on it right now, but I do anticipate others will run into this and they're not going to be able to figure out why firefox keeps dying, so... This bug is filed for the future. I don't mind if you close it or whatever. > Are you using the Wayland session, or the X11 session? Wayland. Apologies, I should have mentioned that. Kwin Wayland has gotten so good I've gotten lazy about it :D > Does it happen in a new clean user account using that same session type? No :( Usually I won't even report something like this unless I can repro it on a live CD so it's clean... but the live CD didn't have all the effects (perhaps because run as a VM, with no GPU?) so I couldn't get KDE in the state that triggers it for me. I filed this in spite of the poor quality of this report, because it's been plaguing me ("Why the heck does FF keep freezing up like this?"... weeks later, "OH! It's when I've minimized them all!") and I know it'll be tricky for the next person to solve.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
TL;DR: Resolving this for now, I'll re-open if needs be. Thanks a bunch for helping me out, Nate! I've been hesitant to post a conclusion too soon, in case this is really still broken, but it appears to have been fixed with firefox 127.0.2 (upgraded from 127.0.1). This is a hotfix that fixes the stuttering video bug. I've had this freeze bug since about that time, too. I guess they're the same bug, different symptoms? Seems like a stretch, but... I haven't had a single freeze since upgrading, and it was constant before. It must be fixed.