wow crashes, error report included

sry double post. pls remove.

Hello,

Can you send me crash reports (in folder "C:\Program Files (x86)\World of Warcraft\Errors\" (the txt file). Send me if by private message (don't put it in public).

Thank you.

Thank you for the  crash files.

I don't think than problem was caused directly by WRobot (but I could be wrong).

Do you get this problem all the time (if you can give me frequency)?

If you can, try to switch directx version in wow (directx 9 to  11).

Try to disable all wow addon.

Try also to relauch wow from time to time (some wow process was run for more than 48 h).

If you can also watch if the memory used by wow process (compare the RAM used when just launched and after 10 hours) (if I am not mistaken, you launch  several wow, and I could see that your ram memory was use 90%, this is  much).

If you see commons points between the crashes (the same used fightclass, the same profile...)

Hi droidz,

thanks a lot for your fast reply.
just some remarks from my limited understanding. I already disabled all addons. Yes i do have several instances of wow running. They all run in minimal graphics settings. The usage of ram (of all wow and wrobot instances included) normally settles between 6 and 7 GB. That is quite a lot but still below the available physical ram.
The crashes happen about once a day. Its hard to tell because i dont keep exact track of which wow crashed when. But there is hardly a day whith out several instances crashin. In principle I would like to let the wow run as long as possible and mostly unattendet. I will try to relaunch wow more often.

The crashes also still happened with no addons loaded and only one wow instance running.
May be it has something to do whit applying the hook. Today after the wrob update. When i tried to restart wrob (clean close of the bot, wow still running, updating wrob, restarting and reaplying wrob to wow instance) the wow instances crashed immediately (same error message) after starting the bot.

I will try more bugtracking to find more hints on when exactly the crashes happen.
It would be very nice if this would be resolve because it makes running the bots "unattendedly" very unrelying.
Thanks for your work sofar.

Best regards
Highco

Since when do you have this problem?

this actually happens persistently since i got back to botting some weeks ago (earliest error logs are from mid oktober 2015).

I just found that the RAM usage for some of the wow instances increased during runtime for some reason. The fps settings have been reset during runtime to higher values. Maybe while zoning, maybe during relogging. But i doubt that this is due to anything from wrob.
Ram usage might be a problem therefore.

Hello,

I come back here to ask you if you still have this problem (if you find the cause, or if you think that the problem is caused by WRobot)?

hi,

sry i didnt check this thread and found your post just now.
The problem still happens. I didnt have the time to do much debugging, but i dont think that it has anything to do with wrob.
For some reason WoW tends to accumulate ramusage during runtime and at some point it probably reaches an upper limit for the application and throws up errors.
If i run a single instance this happens after some days (WoW crashes but WoWs ramusage (above 1.5Gig) is far below the overall available ram on the machine (8Gig) ) if i run a bigger number of WoWs simultaneously (6) it happens after 6 to 8 hours.
I am running a memory cleaning program now, that wipes the ram every 5 minutes which enabled me to run several WoWs (6) for the duration of about a day without an error.
Right now i just restart the WoWs on a daily basis. Not the best workaround but acceptable.
The issue that some of the WoW settings (in particular the max fps boundary) gets reset at some point is probably also not related to Wrob but a WoW problem. Right now i take care of this by firing a macro every some minutes to put the boundary back in place.

Since this seems to be a very particular problem i dont think that it is neccesary for you to spent extended time on it.
Still it would be of interest whether anybody else is able to reproduce this behavior or has similar issues.

I didnt spend much time on botting during the past weeks as soon as i get back to it i will do more bugtracking and get you informed.

Best regards and a happy and succesfull new year.
highco

Hello, I have written this plugin and I have think at you: http://wrobot.eu/files/file/622-memory-clean/