-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory corruption, presumably from grob bitmaps #1115
Comments
The problem appears to be really nasty, since it seems like a live garbage collected pointer ( More specifically:
(The four bytes overhead is: 1-byte for ID, 2-bytes for 305, one byte for 52) The problem is that
|
So it's really a matter of |
The current
One level up, it's
This is consistent with expectations. One level up, we are in
|
Above that, we are in stack rendering code, so we are rendering an equation as a transient object through |
That theory would explain why we only see that in the solving menu, which is practically the only place with a transient object being drawn. |
Running the test suite, occasional crash / assert solving equations:
Breakpoint in
object_error
shows that the problem is in graphic rendering:The object is a bit after the graphic object, and that its content has been overwritten by what looks like bitap data:
The object was valid before the invokation of graphing functoin, so this seems to confirm that there was some kind of drawing outside of bounds.
The text was updated successfully, but these errors were encountered: