anoobis
2015-03-04 02:49:47
Hey guys I've been running HoodzFigher https://villavu.com/forum/showthread.php?t=99977 and run into an interesting problem I hope to understand. I'm posting here because it seems to be and aerolib/osbuddy interaction rather than script specific. Osbuddy crashes followed by script termination with debug information:
Range check error at line 66
and sometimes
Error: Out of memory at line 66
Execution failed.
The following DTMs were not freed: [0]
The following bitmaps were not freed: [0, 1, 2, 3]
Line 66 is referring to AeroLib/core/engine/ColorEx.simba:
This can be reproduced with some consistency by logging either in or out AFTER you start the script but before you finish the setup form. It does however happen occasionally while running. When the script errors out OS buddy closes and an error log is created(http://pastebin.com/0L6Gs4c4).
The error log suggests enabling minidumps (Win7 64) which looks easy enough to do I'd just like to understand more what is happening before I go changing things. What exactly is the OSBuddy/script interaction that causes OSBuddy to crash, and why is it random to some extent? Is there an underlying issue to be examined? I have so far been unable to produce the crash in scripts outside of hoodz fighter.
Thanks much for any information,
anoobis
Range check error at line 66
and sometimes
Error: Out of memory at line 66
Execution failed.
The following DTMs were not freed: [0]
The following bitmaps were not freed: [0, 1, 2, 3]
Line 66 is referring to AeroLib/core/engine/ColorEx.simba:
55| function TColEx.findIn(Area: TBox; var Point: TPoint): Boolean;
56| var
57| tmpCTS : Integer;
58| begin
59| tmpCTS := getToleranceSpeed();
60| if ((Self.hMod <> 0.2) or (Self.sMod <> 0.2)) then
61| begin
62| setColorToleranceSpeed(2);
63| setToleranceSpeed2Modifiers(Self.hMod, Self.sMod);
64| end;
65| checkAreaBounds(Area);
66| Result := findColorTolerance(Point.x, Point.y, Self.Col, Area.X1, Area.Y1, Area.X2, Area.Y2, Self.Tol);
67| setColorToleranceSpeed(tmpCTS);
68| end; This can be reproduced with some consistency by logging either in or out AFTER you start the script but before you finish the setup form. It does however happen occasionally while running. When the script errors out OS buddy closes and an error log is created(http://pastebin.com/0L6Gs4c4).
The error log suggests enabling minidumps (Win7 64) which looks easy enough to do I'd just like to understand more what is happening before I go changing things. What exactly is the OSBuddy/script interaction that causes OSBuddy to crash, and why is it random to some extent? Is there an underlying issue to be examined? I have so far been unable to produce the crash in scripts outside of hoodz fighter.
Thanks much for any information,
anoobis