Calling correct delete function on deletion of gobj #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Info
Originally, the
__del__function ofgobjcalledsuper(gcurve, self).__del__(), whilegcurveis inherited fromgobj, sogobj.__del__()is being called, again.This caused an infinite loop, resulted in
RecursionError, as the recursion depth limit of Python was hit.I think this is a typo, and
super(gobj, self).__del__()is what we expect.Step to reproduce
Using the original code, the error can be reproduced with just two lines of code:
After closing the browser, Python deleted the
curve1object, and thus triggered the bug.