Your message dated Fri, 28 Aug 2026 17:50:04 +0200
with message-id <[email protected]>
and subject line Re: Bug#994124: cinnamon: Quick consumption of memory after a
disk unmount
has caused the Debian Bug report #994124,
regarding cinnamon: Quick consumption of memory after a disk unmount
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
994124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994124
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cinnamon
Version: 4.8.6-2
Severity: important
X-Debbugs-Cc: [email protected]
I have observed (at least since the beginning of the August, therefore this
should not relate to the release of Bookworm) that sometimes my Cinnamon
session crashes.
Now I have found that it happens quite reproducibly when I unmount an SD card
(which was mounted automatically) through the bottom panel menu. No other
such mounts need to be present.
After the unmount, the CPU usage of the `cinnamon --replace` process severely
grows and it slowly starts eating memory, until it gets killed by earlyoom.
Restarting it with Ctrl-Alt-Esc brings the Cinnamon back and remedies the
problem.
It seems that .xsession-errors may contain important hints to the cause as it
gets spammed with loads of occurrences of this messages (with nothing of
merit preceeding it):
(cinnamon:210223): Cjs-CRITICAL **: 12:48:57.797: JS ERROR: Error: second
argument to Lang.bind() must be a function, not undefined
bind@resource:///org/gnome/gjs/modules/script/lang.js:75:15
_sendNotification@/usr/share/cinnamon/js/ui/placesManager.js:169:61
_removeFinish@/usr/share/cinnamon/js/ui/placesManager.js:293:14
I have also tried to get a backtrace, but not sure if it is useful (at another
attempt I got a quite different one):
(gdb) bt
#0 0x00007fd3cf5de3ff in __GI___poll (fds=fds@entry=0x7fff80037b18,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007fd3cdd36d02 in poll (__timeout=-1, __nfds=1,
__fds=0x7fff80037b18) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2 _xcb_conn_wait (c=c@entry=0x5589cb2d57b0,
cond=cond@entry=0x5589cb2d68e0, vector=vector@entry=0x7fff80037c10,
count=count@entry=0x7fff80037c0c) at ../../src/xcb_conn.c:480
#3 0x00007fd3cdd37381 in _xcb_out_send (count=<optimized out>,
vector=<optimized out>, c=0x5589cb2d57b0) at ../../src/xcb_out.c:464
#4 xcb_writev (c=c@entry=0x5589cb2d57b0,
vector=vector@entry=0x7fff80037c70, count=-2147255284, count@entry=3,
requests=requests@entry=43) at ../../src/xcb_out.c:412
#5 0x00007fd3cf804eae in _XSend (dpy=0x5589cb2d4540, data=0x7fff80037ca0
"\367\271\005\200\377\177", data@entry=0x0, size=size@entry=0) at
../../src/xcb_io.c:578
#6 0x00007fd3cf804fc9 in _XEventsQueued (dpy=dpy@entry=0x5589cb2d4540,
mode=mode@entry=2) at ../../src/xcb_io.c:423
#7 0x00007fd3cf7f6931 in XPending (dpy=0x5589cb2d4540) at
../../src/Pending.c:55
#8 0x00007fd3cf0ad3bf in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#9 0x00007fd3cfab5f6f in g_main_context_prepare
(context=context@entry=0x5589cb2cd1f0, priority=priority@entry=0x7fff80037df0)
at ../../../glib/gmain.c:3657
#10 0x00007fd3cfab69cb in g_main_context_iterate (context=0x5589cb2cd1f0,
block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at
../../../glib/gmain.c:4111
#11 0x00007fd3cfab6dfb in g_main_loop_run (loop=0x5589cb2cee20) at
../../../glib/gmain.c:4329
#12 0x00007fd3cf70b8fa in meta_run () at core/main.c:619
#13 0x00005589c9e4a7d8 in main (argc=<optimized out>, argv=<optimized out>)
at ../src/main.c:381
Strace running on the cinnamon process does not seem too revealing, but the
brk() calls there are obvious sign of the increasing memory consumption.
Best regards
TomaS
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cinnamon depends on:
ii cinnamon-common 4.8.6-2
ii cinnamon-control-center 4.8.2-1
ii cinnamon-desktop-data 4.8.1-2
ii cinnamon-screensaver 4.8.1-3
ii cinnamon-session 4.8.0-3
ii cinnamon-settings-daemon 4.8.5-1
ii cjs 4.8.2-1
ii cups-pk-helper 0.2.6-1+b1
ii dbus 1.12.20-2
ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2
ii gir1.2-accountsservice-1.0 0.6.55-3
ii gir1.2-caribou-1.0 0.4.21-7.1
ii gir1.2-clutter-1.0 1.26.4+dfsg-2
ii gir1.2-cmenu-3.0 4.8.3-1
ii gir1.2-cogl-1.0 1.22.8-2+b1
ii gir1.2-cvc-1.0 4.8.1-2
ii gir1.2-gdkpixbuf-2.0 2.42.6+dfsg-2
ii gir1.2-gkbd-3.0 3.26.1-1+b1
ii gir1.2-glib-2.0 1.68.0-2
ii gir1.2-gnomedesktop-3.0 3.38.5-3
ii gir1.2-gtk-3.0 3.24.30-3
ii gir1.2-gtkclutter-1.0 1.8.4-4+b1
ii gir1.2-keybinder-3.0 0.3.2-1.1
ii gir1.2-nemo-3.0 4.8.6-2
ii gir1.2-nm-1.0 1.30.6-1
ii gir1.2-nma-1.0 1.8.32-1
ii gir1.2-notify-0.7 0.7.9-3
ii gir1.2-pango-1.0 1.48.9+ds1-2
ii gir1.2-polkit-1.0 0.105-31
ii gir1.2-soup-2.4 2.74.0-2
ii gir1.2-timezonemap-1.0 0.4.6-2+b1
ii gir1.2-upowerglib-1.0 0.99.13-1
ii gir1.2-xapp-1.0 2.0.7-1
ii gkbd-capplet 3.26.1-1+b1
ii gnome-backgrounds 40.1-2
ii gnome-themes-extra 3.28-1
ii gsettings-desktop-schemas 3.38.0-2
ii iso-flags-png-320x240 1.0.2-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libc6 2.31-17
ii libcairo2 1.16.0-5
ii libcinnamon-desktop4 4.8.1-2
ii libcinnamon-menu-3-0 4.8.3-1
ii libcjs0 4.8.2-1
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libgirepository-1.0-1 1.68.0-2
ii libgl1 1.3.2-1
ii libglib2.0-0 2.68.4-1
ii libglib2.0-bin 2.68.4-1
ii libgstreamer1.0-0 1.18.4-2.1
ii libgtk-3-0 3.24.30-3
ii libmuffin0 4.8.1-1
ii libpango-1.0-0 1.48.9+ds1-2
ii libpangocairo-1.0-0 1.48.9+ds1-2
ii libstartup-notification0 0.12-6+b1
ii libx11-6 2:1.7.2-1
ii libxfixes3 1:5.0.3-2
ii libxml2 2.9.10+dfsg-6.7
ii mesa-utils 8.4.0-1+b1
ii muffin 4.8.1-1
ii nemo 4.8.6-2
ii network-manager-gnome 1.24.0-1
ii policykit-1-gnome 0.105-7+b1
ii python3 3.9.2-3
ii python3-dbus 1.2.18-2
ii python3-distro 1.6.0-1
ii python3-gi 3.40.1-2
ii python3-gi-cairo 3.40.1-2
ii python3-pampy 1.8.4-2
ii python3-pexpect 4.8.0-2
ii python3-pil 8.1.2+dfsg-0.3
ii python3-pyinotify 0.9.6-1.3
ii python3-setproctitle 1.2.2-2
ii python3-tinycss2 1.0.2-1
ii python3-tz 2021.1-1
ii xapps-common 2.0.7-1
Versions of packages cinnamon recommends:
ii blueman 2.2.2-1
ii cinnamon-core 4.8.3
ii cinnamon-l10n 4.8.3-1
ii gnome-terminal 3.40.3-1
ii libcanberra-pulse 0.30-7+b1
ii metacity-common 1:3.38.0-2
Versions of packages cinnamon suggests:
ii cinnamon-desktop-environment 4.8.3
pn cinnamon-doc <none>
pn python3-opencv <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.8.4-1
Hello,
this was caused by a typo in js/ui/placesManager.js: the "Retry" button
handler was registered as `Lang.bind(this, this.remove())` instead of
`Lang.bind(this, this.remove)`, so remove() was called immediately, and
the failing-unmount path kept re-triggering itself in a loop, leaking
notification objects and eating CPU and memory.
It was fixed upstream in commit 8ddf1a6a2 (linuxmint/cinnamon#11624),
released in Cinnamon 5.8.0, so the first Debian version with the fix is
5.8.4-1. Closing accordingly.
Bookworm (5.6.8-1) and bullseye (4.8.6-2+deb11u1) are still affected.
Thanks for the detailed report, the JS error in .xsession-errors was what
pinpointed it.
Regards,
Fabio Fantoni
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
