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 stack trace.

-- 
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 accountsservice

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1966905/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to