GNOME Bugzilla – Bug 791655
background: don't leak wall clock when background changes
Last modified: 2017-12-15 15:58:04 UTC
The background code allocates a GnomeWallClock when its first created, but neglects to drop a reference to that clock at destroy time. The undestroyed clocks lead to a timerfd leak that eventually prevents the shell from functioning.
Created attachment 365590 [details] [review] background: don't leak wall clock when background changes
Review of attachment 365590 [details] [review]: this seems like it should be enough, but see also bug 790531
*** Bug 790531 has been marked as a duplicate of this bug. ***
alright, I think attachment 365590 [details] [review] is the better way to go because wall clocks aren't expensive to create, and so don't really need to be cached. I do thing attachment 365590 [details] [review] would maybe make sense if some widely deployed versions of GnomeWallClock did leak timerfds, since it would mitigate that bug. will push mine
Attachment 365590 [details] pushed as 94b96f8 - background: don't leak wall clock when background changes