Ensure uctypes data isn't GC'd prematurely #14
Merged
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.
MicroPython's GC requires that a pointer to the beginning of an allocated chunk has to be kept somewhere in another reachable object, or the chunk can be freed when GC happens.
However, with uctypes nested structures, this was not necessarily the case. For example, before this PR, you could lose the contents of a
pnSizeobject:After this PR, the correct value of
(8, 12)is printed.