Discussion
![Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:](https://media.infosec.space/infosec-space/accounts/avatars/113/605/038/999/034/961/original/d2ed8d9ebc60820e.jpeg "Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:")
well this is totes weirdarse 😮🤯
in 
each of Masto, Phanpy, & Statuzer, operate well, with pooter's cpu & gpu at low %
otoh...
in 
Masto & Phanpy operate well, with pooter's cpu & gpu at low %
and
in Statuzer operates well, with pooter's cpu at low %
but
in #Statuzer operates well, with pooter's gpu at very high % [always above 80% & frequently above 90%]
i don't know if this is a problem, per se, but it seems... wrong?
🤨🤷♀️
cc: @statuzer
@MsDropbear42 @statuzer it makes no sense! now, abruptly, the high gpu% on Statuzer in has gone away again - it's back to normal
there's been no Nightly update, nor #Statuzer update, since my OP, so... i have no logical explanation 😮🤯
Update
Aha, a big clue! just as i was about to post, someone Liked one of my posts, triggering the Statuzer Notification sound effect... which instantly shot the gpu% right back up to 90%+, & it has not come back down. ie, based only on coincidental timing, i wonder if Statuzer's code to make the sound when notifications trigger, is not being "released" again afterwards?
@MsDropbear42 hello 😊 i'll take a look at this. have you observed this in FF too when a notification occurs ?
@statuzer thank you. i only launched briefly yesterday to test this, but for those brief times when its gpu% remained low for Statuzer, iirc no Notifications had occurred. i am posting this reply to you my next morning, in , but as soon as i post this i shall launch ordinary & use it until some Notifications arise, to then observe if its gpu% also goes nuts.
btw, halfway thru typing this post, someone Liked another of my posts, & the gpu% instantly jumped to ~90% & has not come back down... so whatever is going on, it seems repeatable.
also btw, this morning my had another of its 2X daily updates, yet the problem persists, so atm i cannot say if the fault lies with #FirefoxNightly or #Statuzer 🤷♀️🤯
another btw; once the persistent high gpu% has been triggered, it only stays that way while i remain on my Statuzer tab; if i change to any other tab, the % plummets back down to normal... but then returning to my Statuzer tab jumps it back up high again
@MsDropbear42 @statuzer oh, this might be a big clue! atm i'm still in , but after that last post, before launching , i decided to have a look at that Notification i'd mentioned. i use multiple Spaces in Statuzer [a brilliant feature, thanks for it!], & in my Space 1 i keep the Notifications column permanently visible. so, i went to Space 1, looked at that Notifications column, saw via the highlighted vertical bar which one it was, then clicked the ✅ to clear it... & immediately the high gpu% dropped back down to normal. so... i as a non-coder now intuits that something in the code is wrongly remaining active after the Notification occurs, driving up gpu%, & only becomes "free" once the Notification/s is/are acknowledged.
now i shall try ...
@MsDropbear42 @statuzer news from
, except:so, there's some detail differences, but overall i'd say the behaviour is a close enough correlation with Nightly to consider it probably a common-cause factor in #Statuzer... ?
@MsDropbear42 @statuzer oh, also... by the time i had written that preceding reply & posted it, the gpu% has now returned to the 20s, ie, it ended up back where Nightly is, but somehow took a bit longer to get there 🤯
@MsDropbear42 thanks a lot for all this tests, i'll have a look at this soon.
@statuzer hello again. i have been thinking more about this, & feeling bad for you. i suspect it actually is not worth your effort to bother with. initially before i noticed the exact correlation with Notification events, i was just confused & worried. however ever since "proving" a 100% success rate with the gpu% dropping back down to normal levels each time i acknowledge any active Notifications, it seems to me to be an entirely acceptable management tactic. so... maybe i should not have bothered you about it... & maybe you can just forget about it now & regard it as a non-problem?
@MsDropbear42 i'll inspect this anyway, if there's something to improve, i'll try to. Thanks again ! :)
i prefer not having to drop back down to
to avoid this symptom, coz i always prefer 
. though i dunno if it is a danger to run the gpu semi-permanently at very high % usage, given i spend so much time in fedi, for now i've reluctantly chosen to revert to std Masto in lieu of the lovely #Statuzer. sassen frassen rassen
cc: @statuzer