Jump to content

  • [TBC] Memory leak?

    Matenia

    By Matenia

      • Product: WRobot General Type: Bug Status: Unconfirmed
     Share

    In TBC, it seems after a while wRobot just jumps to 15-30% CPU usage per instance. Only a full restart of wRobot solves this. I have tried with and without my plugin. 
    I don't really understand why this happens, but on vanilla everything is fine.

     Share
    Go to bug reports

    User Feedback

    Recommended Comments

    Droidz

    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.

    Link to comment
    Share on other sites
    Matenia
    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.

    Link to comment
    Share on other sites
    Matenia

    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.

    Link to comment
    Share on other sites
    spector800

    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

    highcpu.png

     

    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)
     

    Link to comment
    Share on other sites
    Droidz
    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

    Link to comment
    Share on other sites
    Floood0
    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? 

    Link to comment
    Share on other sites


    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 account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...