1.38 Fanart cause my Mediaportal to start up very slowy (5 Viewers)

[Hsenag]

Hi all,
I've been using MediaPortal for years now, and suddenly it started taking an incredibly long time to start up or shut down. Since, as always, the “Loading plugins” message appears when it responds slowly, I did a clean install and added the plugins I use (via MpeInstaller) one by one to find the culprit, and it turns out that Fanart Handler is what’s making my system very slow at startup. Furthermore, once I’ve added it, if I remove it (still using MpeInstaller), the system remains slow; I have to do a fresh install for it to start responding normally again. I’m not sure where to look to fix this strange problem. Thanks in advance for your ideas and suggestions.
Take care

PS: I forgot to mention that I also tried installing version 1.37, but the slowness issue is still there, so I switched back to 1.38.3.

 

[ajs]

The first scan may use up a few resources, but it should run smoothly afterward. Especially since the scan runs in the background and pauses when playback begins.

 

[Hsenag]

Thank you for your interest, but I waited several weeks, putting up with the loading and unloading times, before seriously investigating the cause of this delay. So this isn't a temporary issue.
I’ve been running MediaPortal without the fanart handler for a few days now, and the loading/unloading times have returned to what they were before the issues started. I can get by just fine this way (though the wallpaper images are missing, which is a shame), but I like to understand the root cause of the problems. As a retired IT professional, I’ve retained a passion for understanding and fixing things on my own, and none of this explains why removing a plugin via MpeInstaller leaves the system “unstable”.

 

[ajs]

why removing a plugin via MpeInstaller leaves the system “unstable”.

I haven't noticed that kind of behavior, so I don't know. But if the system isn't stable, it writes error messages to the log.

Generally speaking, all actions are recorded in a log file. But you're the first person to encounter this problem.