https://bugs.kde.org/show_bug.cgi?id=489652
--- Comment #2 from pallaswept <pallasw...@proton.me> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
