Control on DBus-daemon virtual memory usage ballooning
David Rheinsberg
david.rheinsberg at gmail.com
Fri Sep 11 14:15:10 UTC 2020
Hi
On Fri, 11 Sep 2020 at 11:03, Adrian Szyndela <adrian.s at samsung.com> wrote:
> On 10 Sep 2020 at 08:02, David Rheinsberg <david.rheinsberg at gmail.com> wrote:
> > On Thu, 10 Sep 2020 at 01:21, Hailun Tan <dearambermini at gmail.com> wrote:
> >> It mentioned that D-Bus never freed its data.
> >
> > The dbus-daemon process uses memory-management like any other common
> > Linux process. The memory-allocator is taken from glibc. This
> > allocator reserves a pool of data which it hands back to the kernel
> > only when fragmentation and usage permit it.
>
> I think the internal memory pools, managed by DBusMemPool, may be involved here.
I agree, DBusMemPool may behave non-optimally. Though, to analyse a
situation I would need a description of the symptoms. The initial
report talks about "growing VM usage", which is quite unspecific.
Without any actual data, I don't see the point in speculating what
could go wrong.
Thanks
David
More information about the dbus
mailing list