** Changed in: accountsservice
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966905
Title:
Valgrind memory errors in gnome-shell 42 from
I think this is triggered by valgrind because it leads to slowdowns, but
the bug is indeed there.
We can handle it in a later upload I think, but due to gslice and the
randomness of these memory errors, I wouldn't be shocked if this is
actually presenting right now in the wild with a different
Dropped severity - there are no reports of this crashing in the wild,
that I can find.
** Changed in: accountsservice (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Could you do the suggested change anyway and keep it around, maybe you
will hit the bug again with it in place?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966905
Title:
I never narrowed down the test case to reproduce this -- it just
happened once in every few attempts to valgrind gnome-shell.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Upstream gave some debugging hints
'So the only unref call has a matching ref call pair. This means it
shouldn't lead to the object getting freed. But between those two calls
the property notify handlers get run, etc. It's at least conceivable to
me that one of those handlers is accidentally
Reported upstream on
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/103
** Changed in: accountsservice (Ubuntu)
Importance: Undecided => High
** Bug watch added:
gitlab.freedesktop.org/accountsservice/accountsservice/-/issues #103
