Ubuntu
libcanberra package

80% (512MB) of gnome-shell's memory mappings at start up are due to PulseAudio

Bug #1759497 reported by Daniel van Vugt
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
PulseAudio
New
Unknown
gnome-shell (Ubuntu)
Confirmed
Undecided
Unassigned
libcanberra (Ubuntu)
Confirmed
Undecided
Unassigned
pulseaudio (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

80% (512MB) of gnome-shell's memory mappings at start-up are due to PulseAudio.

This seems excessive.

Memory profile from Google heap profiler attached.

Tags: performance
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Although this may not be a bug. It might just be reserved address space with very little physical memory impact.

Revision history for this message
In , Daniel van Vugt (vanvugt) wrote :

Created attachment 138392
gnome-shell-all-mmaps-at-startup.pdf

80% (512MB) of gnome-shell's memory mappings at start-up are due to PulseAudio. This seems excessive.

Memory profile from Google heap profiler attached.

Although this may not be a bug. It might just be reserved address space with very little physical memory impact...?

Revision history for this message
In , Daniel van Vugt (vanvugt) wrote :

Looks like maybe gnome-shell's use of libcanberra might be one of the triggers.

Bug Watch Updater (bug-watch-updater)
Changed in pulseaudio:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/159

Revision history for this message
In , Tanu Kaskinen (tanuk) wrote :

Each "mempool" in pulseaudio is 64 MB by default, and there's one mempool per client. Maybe gnome-shell has multiple connections to pulseaudio? 8 connections sounds excessive, though... Maybe the server's own mempool is visible in the client memory mapping too, so perhaps two mempools per connection are visible in the client memory map. 4 connections sounds still a bit much, though.

The mempools should indeed not have full "physical" impact unless they're actually fully used.

What if you set "shm-size-bytes = 33554432" (i.e. 32 MB) in /etc/pulse/client.conf and /etc/pulse/daemon.conf and reboot? Does the gnome-shell memory usage go down by 256 MB?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Changed in libcanberra (Ubuntu):
status: New → Confirmed
Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Gitlab-migration (gitlab-migration) wrote :

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/92.

Bug Watch Updater (bug-watch-updater)
Changed in pulseaudio:
status: Confirmed → Unknown
Daniel van Vugt (vanvugt)
Changed in pulseaudio:
importance: Medium → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in pulseaudio:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.