Results 1 to 10 of 14
13.03.2013, 05:05 #1
Could not read bytes from 29DB5E7C !
Almost everytime I use Honorbuddy, I get...
System.AccessViolationException: Could not read bytes from 29DB5E7C !
Why does this happen so much? A lot of the times HB will crash and I will try to "report the error", but even THAT gives me an error. It says I have reported too many errors (go figure).
It's even gotten to the point to where if I minimize HB to my tray, it will crash and quit working. I have tried a fresh HB install many times and it still does this.
Here's my Log:
1208 2013-03-12 20.38.txt
Edit: I noticed something. If I load WoW, then load HB then close HB for whatever reason (don't need it, it crashed, etc).. then I load HB again.. I will get the "System.AccessViolationException: Could not read bytes from 29DB5E7C !" error. If I close Honorbuddy, I *have* to close and restart WoW for HB to work the way it should. Maybe that will help.
Last edited by Vastator; 13.03.2013 at 05:30.
13.03.2013, 06:48 #2
it seems to be your combat rotuine.
make a fresh install and upload a full log as an attachment please.
[Guide] How to attach your log
13.03.2013, 07:02 #3
13.03.2013, 07:05 #4
yea, but you have another combat routine thats installed that causing issues.
13.03.2013, 23:25 #5
13.03.2013, 23:33 #6
There are several HB API calls that cause that. I debugged it in my plug-in once. It was Styx.WoWInternals.WoWObjects.WoWUnit.get_Location( ) -> Styx.MemoryManagement.ExternalProcessReader.ReadBy tes(IntPtr address, Int32 count, Boolean isRelative) that was causing the exact same Exception from time to time. I am however not sure if that is the Location bug (it might be Subzone or Zone too, as I've seen that there too). I already reported that but I am not sure whether it was fixed.
HB shuts down with "Could not read bytes from 000007D8 ". Why?
Last edited by Keanu; 13.03.2013 at 23:41.Keanu
Stop looking at my signature. Get outside and start living.
13.03.2013, 23:53 #7
Try reloading the Ui, i know it seems silly but i think the lua get messed up from time to time and this generally fixes it for me.
14.03.2013, 00:08 #8
So I would suggest turning off ALL mods and using Singular and see if you still get the error. If you do not.. then you know where the problem is.
14.03.2013, 00:51 #9
14.03.2013, 05:58 #10