New Badge Overlay plugin

[eMoOak 8]

37 minutes ago, Amanade3 said:

This patch should fix it. but if you're still seeing high CPU after updating, let me know and I'll dig into what else might be causing it.

Hi, I’ve just tested version 1.3.5.0 after your fix.

Unfortunately, the CPU usage issue is still present. With EmbyNewOverlay enabled, the EmbyServer process goes to around 100% CPU continuously. As soon as I disable the plugin, CPU usage immediately returns to normal.

I also confirmed that Emby is actually loading version 1.3.5.0.

So it looks like the DateTime.MinValue / DateTimeOffset issue was fixed, but there is another issue causing the high CPU usage.

There are no obvious exceptions in the Emby log while this is happening, which makes it a bit harder to identify.

I’ve had to disable the plugin again for now because of the CPU usage.

[Neminem 1826]

@eMoOakI guess @Amanade3 would need your hardware info. 

And server logs with debug logging turned on. 

[Amanade3 69]

Well I suspected there is another issue causing your CPU to run at 100% because while testing it on my PC with no premiere date, I didn't have a CPU running at 100%.  like @Neminemsaid can you dump the emby server log and your hardware info. And i have one question for you. Is the v 1.3.4.0 the first version you tried on? and maybe one thing to try..... Try switching off some master switches like most watched, studio logos and the like and test the results.

 

Edited 21 minutes ago by Amanade3

[eMoOak 8]

The issue seems to be specifically triggered by the Seerr library synchronization. With EmbyNewOverlay enabled:

Seerr stopped → CPU normal
Seerr running, library sync disabled → CPU normal
Seerr running, library sync enabled → EmbyServer CPU goes to ~100%

So it looks like the large number of library/season/episode requests generated during Seerr's library synchronization triggers excessive processing in EmbyNewOverlay.

[Amanade3 69]

Oh so it was seerr after all? glad you figured it out your self.

[eMoOak 8]

3 minutes ago, Amanade3 said:

Oh so it was seerr after all? glad you figured it out your self.

Not exactly. Seerr itself doesn't cause the high CPU usage.

The important part is the interaction with EmbyNewOverlay:

• Seerr stopped + EmbyNewOverlay enabled → normal CPU
• Seerr running + library sync disabled + EmbyNewOverlay enabled → normal CPU
• Seerr running + library sync enabled + EmbyNewOverlay enabled → ~100% CPU

So the library synchronization in Seerr appears to trigger the issue, but I suspect something in EmbyNewOverlay is being executed excessively when Seerr scans the library.

If I disable EmbyNewOverlay while keeping Seerr's library sync enabled, CPU usage also stays normal.

So I don't think Seerr itself is the problem; rather, Seerr's library synchronization seems to trigger a problem in the overlay plugin.