[TBC] Memory leak?

Observed in Quester product, have not tried others.

Hello, in tbc all items seems to be keep in memory (in the objectmanager), when you go to big city (with a lot of players and a lot of items (equipped)) or after few hours you can get bigger CPU usages.

1 hour ago, Droidz said:

Hello, in tbc all items seems to be keep in memory (in the objectmanager), when you go to big city (with a lot of players and a lot of items (equipped)) or after few hours you can get bigger CPU usages.

Is there any way I can trigger a clean on the WoW ObjectManager? A /run ReloadUI() ingame does not work, unfortunately.

Change continent (dead? logout?) seem to clean objectmanager.

Can you try with the new update and tell me if this change something about CPU usage.

Tested the update. It gets to 15% CPU (maybe more if I let it run longer).
Is there maybe some bug in TBC version? I cannot really imagine vanilla and wotlk objectmanager working so differently from TBC.

I'm seeing this as well, although it's on the Vanilla client so not sure if related:

Also using Quester product (FNV's logic).

The CPU spike occurs when first logging into the product (License Keys Management Login), where it goes from ~4-5% CPU to 15-18%, even without running the actual quester code.
Logs don't show any errors being thrown at this time

Edit: Logs now showing this error:

[E] 13:41:31 - GetReqWithAuthHeader(string url, String userName, String userPassword): System.Net.WebException: The remote server returned an error: (400) Bad Request.
   at System.Net.HttpWebRequest.GetResponse()
   at robotManager.Helpful.Others.GetReqWithAuthHeader(String url, String userName, String userPassword, String othersValue)
[E] 13:41:40 - GetReqWithAuthHeader(string url, String userName, String userPassword): System.Net.WebException: The remote server returned an error: (400) Bad Request.
   at System.Net.HttpWebRequest.GetResponse()
   at robotManager.Helpful.Others.GetReqWithAuthHeader(String url, String userName, String userPassword, String othersValue)
 

On 7/10/2018 at 7:25 PM, Matenia said:

Tested the update. It gets to 15% CPU (maybe more if I let it run longer).
Is there maybe some bug in TBC version? I cannot really imagine vanilla and wotlk objectmanager working so differently from TBC.

This problem is only in TBC, I ignore if it is server or client bug, and I ignore how to fix that

On 7/12/2018 at 8:22 PM, Droidz said:

This problem is only in TBC, I ignore if it is server or client bug, and I ignore how to fix that

So, what we should do now? Botting with 3 bot or writting addon what will restart wow every 30 min?