Closed jiangqii closed 1 year ago
ok,i found that will happen in this: libmatemixer-1.20.1/backends/alsa/alsa-backend.c
364 //if (g_hash_table_contains (alsa->priv->devices_ids, id) == TRUE) {
365 if (FALSE) {
366 snd_ctl_close (ctl);
367 g_warning("========= 44444444 sn_ctl_close =========");
368 return FALSE;
369 }
370
371
372 device = alsa_device_new (card, snd_ctl_card_info_get_name (info));
373 g_warning("========= alsa_device_new 55555 =========");
374
375 if (alsa_device_open (device) == FALSE) {
376 g_object_unref (device);
377 snd_ctl_close (ctl);
378 g_warning("========= g_object_unref,snd_ctl_close 66666666 =========");
379 return FALSE;
380 }
Closing this one as leak seems in libmatemixer.
Expected behaviour
mem no longer increase
Actual behaviour
mem increase
Steps to reproduce the behaviour
38168 40000 50000 ....
MATE general version
1.20 1.24
Package version
mate-media 1.20.2-1 arm64 mate-media_1.24.1-1_arm64.deb
Linux Distribution
debian buster
Link to bugreport of your Distribution (requirement)