highco

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

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.

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

sry double post. pls remove.

Hi Droidz,

thanks for your fas reply.
Blacklisting the zone instead of the mob is unfortunately not always possible. Sometimes that would block a passage to the rest of the profile. Also blacklisting the zones does not always work reliably. The bot seems not to respect blacklisted zones fully in long moves (e.g. going to town) and when moving to farm spots.
Unfortunately this also wont solve the issue that the bot will get locked on a bugged mob for hours when unattended, unless it automtically blacklists bugged mobs reliably.
Thanks for your effort anyway

best regards
Highco

Thank you for the fast fix. I didnt get any more freezes and no more error messages so far.

It still tends to forget the character specific product settings on restart (gatherer, grinder or schedule ...) though.

ok seems to run stable now. Thanks again.

quick update of the situation so far.

After replacing the meshes directory with the downloaded one, wrobot still crashed about two times (sry i missed to get the error message).

Since the update it runs very stable, no more crashes so far.

Thanks for the great support.

Thank you for the fast reply.

I downloaded the meshes.zip that you recommended and will test it now.

By the way deleting the Meshes directory to force new download (what i did before) did not resolve the issue for me.

ok i will send the logs

Hi Droidz,

thanks a lot for you answer. I only realized after my posting that there was the webserver transfer and assumed it might have something to do with it.

the error didnt happen again since then.