High CPU usage/runaway process by MXPI after closing.

[turfymiler]

25.09.1 appeared in MX Updater for me today. I installed it but the problem is still with me. The package Installer process doesn't stop when I close the application and suddenly takes up 25% of CPU after a couple of minutes. Each time I open MXPI again in a session another 25% of CPU gets used.

[wdscharff]

I've tried every variation mentioned here, from opening and immediately closing the program to doing nothing and waiting, to doing something and quitting/or waiting and quitting later.
No matter what I do, after 1-3 seconds the memory is freed, MXPI disappears from the System Monitor, and my PC displays the usual idle values.

Since Conky is configured on my system so that I can directly monitor the memory requirements and utilization of all cores, including the top 5 (or 10 if needed) applications, I would have noticed this behavior immediately.

[turfymiler]

I've found what was causing my problem with MX Package Installer. I use OpenSnitch and had set it to deny /usr/bin/flatpak as I don't use flatpaks. In an earlier post I mentioned that I thought I'd turned off flatpaks somewhere. Just occurred to me this morning that OpenSnitch is where I'd done that.

I changed /usr/bin/flatpak in OpenSnitch from 'Always deny' to 'Always allow', started MXPI from Terminal and closed it. This time I got the prompt back in Terminal and the MXPI process in Task Manager disappeared.

My problem is resolved. I guess not many others use OpenSnitch and decide to deny /usr/bin/flatpak without realising the consequence for MXPI.

@retroD0d0 - could this be the cause of your problem too?

[Eadwine Rose]

Wow.. good that you found the problem! Please click the checkmark in the top right set of buttons of the post that holds the solution to mark the topic solved, this way readers will be taken directly to the solution. Thanks :)

[retroD0d0]

@turfymiler No, I don't use OpenSnitch. Hmmm, this certainly explains why a clean .iso works for you. Glad you managed to resolve the issue your end. It does seem @Adrian was onto something, the MXPI initialisation process, including package list updates, is not meant to be interrupted, manually in my case or by another application in yours. The cleanup function is what appears to hang.

Thanks @wdscharff for taking the time to test on your end for us. As I said, for me, it is every iso, every system, live or installed. The only common factor I can think of between my various installations is my geographic location (Indian Ocean), I was thinking it may be something to do with the way my local repos are configured, but on my fresh/clean/ live iso the default US repos are still configured. Unless it is something else geo-based? System time/region seems correctly configured across installations.

The only other common factor is that my systems are relatively low-spec, my most powerful system is an Intel N100! They all run mx dreamily though, generally speaking, including KDE except for my puny AMD E-350 (Fluxbox to the rescue!)

Personally, it is an issue I can live, now that I am aware, but I would hate for other users to have the issue and not know, it mercilessly gobbles cpu cycles and electricity.

[turfymiler]

@Eadwine Rose - Yes, it's good to have resolved my issue but @retroD0d0 is the original poster and still has their issue. So it wouldn't be right for to mark this topic as solved.

Thank you to all who've posted to help me with the issue I had.

[Adrian]

@Eadwine Rose - Yes, it's good to have resolved my issue but @retroD0d0 is the original poster and still has their issue. So it wouldn't be right for to mark this topic as solved.

Thank you to all who've posted to help me with the issue I had.

Agreed. BTW, you can also uninstall flatpak, you don't need to block it on the firewall...