Bugzilla – Bug 1143132
projectM makes clementine's visualizations a memory hog
Last modified: 2020-05-04 06:55:48 UTC
Afer update to Build 20190723 of tumbleweed, the 20Tb problem has been fixed. But the biggest issue with memory leak is when you turn the projectM visualizer on. In just 5 seconds usage, the memory consumptions increases to few gigabytes and the swap usage keeps on increasing till the machine runs out of memory. The load increases and the machine becomes unresponsive. top - 11:28:23 up 20 min, 5 users, load average: 2.55, 1.83, 1.35 Tasks: 338 total, 4 running, 333 sleeping, 0 stopped, 1 zombie %Cpu(s): 24.0 us, 2.7 sy, 0.0 ni, 68.8 id, 0.9 wa, 0.0 hi, 3.7 si, 0.0 st MiB Mem : 7929.961 total, 129.785 free, 3039.844 used, 4760.332 buff/cache MiB Swap: 8195.996 total, 8165.746 free, 30.250 used. 4558.633 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 28548 mbhangui 20 0 3831228 1.379g 139216 R 106.6 17.81 0:27.68 clementine At the moment I am using clementine by copying the executable from a FC30 build I also have to copy the following shared libraries to have a working music player on tumbleweed libcdio.so.18.0.0 libprojectM.so.2.1.0 libprotobuf.so.17.0.0 libQxtCore-qt5.so.0.7.0 libQt5Solutions_LockedFile-2.4.so.1.0.0 libcryptopp.so.8.2.0 libQxtWidgets-qt5.so.0.7.0 libQt5Solutions_IOCompressor-2.3.so.1.0.0 libQt5Solutions_SingleCoreApplication-2.6.so.1.0.0 libQt5Solutions_SingleApplication-2.6.so.1.0.0 libsha2.so.1.0.1
This bug was originally reported by Manvendra Bhangui in Bug 1141444
Created attachment 811854 [details] Valgrind projectM-pulseaudio on versiom 2.1.0
Created attachment 811855 [details] Valgrind projectM-pulseaudio on versiom 3.1.0 This shows serious memory problems with projectM, it quits on 1000 different errors.
I've noticed a few similar things myself, but the new upstream management does not seem to be overly interested in whatever happens with projectM as plugin. I wish I had a solution other than downgrading.
I've opened an issue with them, 3.1.0 has a serious memory problem See https://github.com/projectM-visualizer/projectm/issues/233
(In reply to Luigi Baldoni from comment #4) > I've noticed a few similar things myself, but the new upstream management > does not seem to be overly interested in whatever happens with projectM as > plugin. > > I wish I had a solution other than downgrading. Seems that they are keen to fix the problem.
This is resolved upstream: https://github.com/projectM-visualizer/projectm/issues/233