What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Error in bot after 3 hours ++ for me

Status
Not open for further replies.
S

snakkes

New Member
Joined
Apr 5, 2014
Messages
548
Reaction score
0
System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory.. Bot ERROR.

I get this error when I run Three Musketeers profile for many hours.

Just for no reason it seems like.

The bot stops and the error message keeps resetting :\

The bot works perfect until this error suddenly for no reason when crafting like game 231 or 176.

Just seems like there is no reason for it either :S

Just that error that comes when I run the bot for over 3 hours ++

Error happens with trinity .24 and .25.

Tried released version and beta version.

Exception when terminating bot thread. System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000198, Size: 12
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(Int Ptr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_Position( )
at QuestTools.MoveToActor.WithinInteractRange()
at QuestTools.MoveToActor.<CreateBehavior>b__30(Objec t ret)
at Zeta.TreeSharp.Decorator.CanRun(Object context)
at Zeta.TreeSharp.Decorator..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Wait..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.Sequence..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.()
 

Attachments

Last edited:
just happened to me too
3 bots have this error every time before create new game, only one continue playing, another two have their windows frozen, and dont running, only this error
 
Kevin Spacey said:
just happened to me too
3 bots have this error every time before create new game, only one continue playing, another two have their windows frozen, and dont running, only this error
Click to expand...

Are you maybe at home and can produce an log asap? :)

And if you find an fix yourself, maybe share it in this thread :)
 
Last edited:
Looks like there is ALOT of people with theese memory problems now...
 
Bump

Looks like more and more people get this error...

Time to step up and FIX it!
 
snakkes said:
Bump

Looks like more and more people get this error...

Time to step up and FIX it!
Click to expand...

Well, if you have done the steps from the other post you replied to, then it may be an issue with the new DB releases or Trinity (not saying the latest ONE, saying more then one version)

But what I can tell you is this. (Just as some FYI/Reference) I run 4 bots 24/7 and I do not have that issue. I run DB .355 and trinity .22 .. Whenever I update I update to a fresh folder so if the new stuff doesnt work out for me, its easy for me to revert back. Since I have not found working versions of DB or trinity better or more stable then the ones I am currently running I just stay with the ones I have.

My Exact Setup:
DB .355
Trinity .22
QuestTools 1.5.24
SimpleFollow .16

(Im not saying it will work for you, but for me it only stops when I stop it to clear out stash, when blizz servers are down for maint or when authentication pops up during a relog)

EDIT - And it isnt that support doesnt want to address this issue.. They are just short handed right now and Tony is out due to an illness/surgery. So I'm just trying to help out a little :)
 
Last edited:
Drazz446 said:
Well, if you have done the steps from the other post you replied to, then it may be an issue with the new DB releases or Trinity (not saying the latest ONE, saying more then one version)

But what I can tell you is this. (Just as some FYI/Reference) I run 4 bots 24/7 and I do not have that issue. I run DB .355 and trinity .22 .. Whenever I update I update to a fresh folder so if the new stuff doesnt work out for me, its easy for me to revert back. Since I have not found working versions of DB or trinity better or more stable then the ones I am currently running I just stay with the ones I have.

My Exact Setup:
DB .355
Trinity .22
QuestTools 1.5.24
SimpleFollow .16

(Im not saying it will work for you, but for me it only stops when I stop it to clear out stash, when blizz servers are down for maint or when authentication pops up during a relog)

EDIT - And it isnt that support doesnt want to address this issue.. They are just short handed right now and Tony is out due to an illness/surgery. So I'm just trying to help out a little :)
Click to expand...

Yup, I know.

But looks like more and more people have this problem :( Even Kevin had it, and he knows what he is doing.

Would you mind uploading your setup so I can try it out? :D
 
No help here Tony?

You answered everyone else thread except here...
 
Last edited:
snakkes said:
Yup, I know.

But looks like more and more people have this problem :( Even Kevin had it, and he knows what he is doing.

Would you mind uploading your setup so I can try it out? :D
Click to expand...

Yes I know that. When you asked me the other day about it I went through the support searching for Process Frozen and Out of sync.. There are many posts in regards to this issue and none of them had a solid "Yes - That fixed it" .. :/ Some said a downgrade fixed, other said they reinstalled their DB and it fixed.

To clarify my previous post: Even with the older versions I am still running I get some red errors in my DB log from time to time, however, as far as I can tell everything appears to continue running properly, so I just ignore them. (I know thats not the issue you are having, you all are actually having freezups/crashing, I just wanted to put that out there so someone doesnt come back and say "This version still shows errors"..etc)

What I would recommend to buddy users in the future, is:
Once you get a KNOWN good setup.. Like lets say next DB version and next trinity version work flawlessly for you. Copy that folder into a backup directory. C:\Backups\DB\ or whatever. This way as more versions come out and you upgrade and or change things, if something gets jacked up you can wipe it, and copy back from your backups folder to your useable directory. I think that is a much better option then upgrading something, it not working as good as it use to and waiting until your issues are fixed in a future release. Depending on how old your computer is, it may take you 15 seconds max to make a backup copy of your DB folder. :) If it takes longer then 20-25 seconds to copy your db folder (last time I did it, it was like 45mb) then your computer is the problem. :D
 
Yea, I just hope Tony or some other mods come around and pick up on this problem.

Looks like many have theese memory problems here :\
 
Drazz446 said:
Yes I know that. When you asked me the other day about it I went through the support searching for Process Frozen and Out of sync.. There are many posts in regards to this issue and none of them had a solid "Yes - That fixed it" .. :/ Some said a downgrade fixed, other said they reinstalled their DB and it fixed.

To clarify my previous post: Even with the older versions I am still running I get some red errors in my DB log from time to time, however, as far as I can tell everything appears to continue running properly, so I just ignore them. (I know thats not the issue you are having, you all are actually having freezups/crashing, I just wanted to put that out there so someone doesnt come back and say "This version still shows errors"..etc)

What I would recommend to buddy users in the future, is:
Once you get a KNOWN good setup.. Like lets say next DB version and next trinity version work flawlessly for you. Copy that folder into a backup directory. C:\Backups\DB\ or whatever. This way as more versions come out and you upgrade and or change things, if something gets jacked up you can wipe it, and copy back from your backups folder to your useable directory. I think that is a much better option then upgrading something, it not working as good as it use to and waiting until your issues are fixed in a future release. Depending on how old your computer is, it may take you 15 seconds max to make a backup copy of your DB folder. :) If it takes longer then 20-25 seconds to copy your db folder (last time I did it, it was like 45mb) then your computer is the problem. :D
Click to expand...

And would it be possible for you to upload what you are running, so I can see if that atleast fix my memory error? :)
 
This time I got lucky and it looks like the game and bot continue even tho it faced the same error as you can see in the log.

For me it looks like this memory error:
06:34:58.590 ERROR Pulsator System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 7E2A102D, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.FastAttribGroupsEntry.GetAttribute[T](Int32 attribute)
at Zeta.Game.Internals.Actors.ACD.GetAttribute[T](Int32 attribute)
at Zeta.Game.Internals.Actors.ACD.GetAttribute[T](ActorAttributeType attributeType)
at Zeta.Game.Internals.Actors.DiaUnit.get_Level()

Comes random at random times, and sometimes it makes the game and bot fail but sometimes the game and bot manage to "work" trough it so it can go on.

Gonna run this log trough the end and see if there is any difference for when the bot manages to "work trough" the error compared to when it not manages to "work trough" it.
 

Attachments

Last edited:
snakkes said:
And would it be possible for you to upload what you are running, so I can see if that atleast fix my memory error? :)
Click to expand...

You should be able to use the latest release and download trinity.22 here:
http://www.thebuddyforum.com/demonbuddy-forum/plugins/trinity/93720-trinity-download-here.html

(I do not think .22 has the adventure mode functionality though, so if you like running rifts/etc it is probably not the version for you) .. I just run questing profiles in campaign mode though so I just run .22 for the time being.
 
Status
Not open for further replies.
Back
Top