eMoOak 9 Posted August 10 Posted August 10 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 1835 Posted August 10 Posted August 10 @eMoOakI guess @Amanade3 would need your hardware info. And server logs with debug logging turned on.
Amanade3 74 Posted August 10 Author Posted August 10 (edited) 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 August 10 by Amanade3
eMoOak 9 Posted August 10 Posted August 10 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 74 Posted August 10 Author Posted August 10 Oh so it was seerr after all? glad you figured it out your self.
eMoOak 9 Posted August 10 Posted August 10 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.
Amanade3 74 Posted August 10 Author Posted August 10 Well this makes it hard to find the cause, if seerr is involved..... I don't even use seerr and i don't know what happens to the plugin during lib sync. I will try to look into it but not gonna promise this will be fixed .
eMoOak 9 Posted August 10 Posted August 10 9 minutes ago, Amanade3 said: can you try it with most watched turned off? Yes. I kept EmbyNewOverlay fully enabled and re-enabled Seerr library synchronization. The only thing I disabled was Most Watched. With Seerr library synchronization running and Most Watched disabled, CPU usage stays completely normal. So it looks like Most Watched is specifically triggering the high CPU usage during the Seerr library synchronization.
Amanade3 74 Posted August 10 Author Posted August 10 Okay good to know, that narrows it down... for now disable most watched... I will look into the issue. 1
WDPR4100 18 Posted August 11 Posted August 11 6 hours ago, Amanade3 said: Okay good to know, that narrows it down... for now disable most watched... I will look into the issue. Indeed, it's the same problem; above all, synchronization takes ages and can even block access (slowing down the server).
Amanade3 74 Posted 22 hours ago Author Posted 22 hours ago New Release V 1.3.5.0 Fixed high CPU usage during library synchronization with Seerr. Added Top Center and Bottom Center positions for badge overlays. Unified the “Most Watched” label across all content types, including movies, series, and episodes. EmbyNewOverlay.dll 1
GrimReaper 5075 Posted 21 hours ago Posted 21 hours ago (edited) 1 hour ago, Amanade3 said: New Release V 1.3.5.0 Added Top Center and Bottom Center positions for badge overlays. 4.9.5.0. stable Not seeing those options, only 4 previously available ones. Edited 21 hours ago by GrimReaper
GrimReaper 5075 Posted 21 hours ago Posted 21 hours ago Hm, possibly version mismatch/wrong dll, maybe this latest version should be 1.3.6.0, as you already had 1.3.5.0. last week? On 8/10/2026 at 5:50 PM, Amanade3 said: New Release V 1.3.5.0 Fix high CPU usage caused by an exception in badge cache-key generation for items with no premiere date. EmbyNewOverlay.dll 1.8 MB · 9 downloads 1 hour ago, Amanade3 said: New Release V 1.3.5.0 Fixed high CPU usage during library synchronization with Seerr. Added Top Center and Bottom Center positions for badge overlays. Unified the “Most Watched” label across all content types, including movies, series, and episodes. EmbyNewOverlay.dll 1.8 MB · 1 download
Amanade3 74 Posted 25 minutes ago Author Posted 25 minutes ago sorry my bad i thought the last one was 1.3.4.0 i will update the version. thanks for pointing that out.
Amanade3 74 Posted 18 minutes ago Author Posted 18 minutes ago EmbyNewOverlay.dll CORRECTION, New Release V 1.3.6.0 Fixed high CPU usage during library synchronization with Seerr. Added Top Center and Bottom Center positions for badge overlays. Unified the “Most Watched” label across all content types, including movies, series, and episodes.
Amanade3 74 Posted 16 minutes ago Author Posted 16 minutes ago 21 hours ago, GrimReaper said: Not seeing those options, only 4 previously available ones. I thought I updated the version from 1.3.4.0 to 1.3.5.0 but apparently the last version was 1.3.5.0 and the new should have been 1.3.6.0 (which is corrected now)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now