Uh oh!
There was an error while loading. Please reload this page.
gh-128923: Use zero to indicate unassigned unique id - #128925
Conversation
In the free threading build, the per thread reference counting uses a unique id for some objects to index into the local reference count table. Use 0 instead of -1 to indicate that the id is not assigned. This avoids bugs where zero-initialized heap type objects look like they have a unique id assigned.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: T. Wouters <thomas@python.org>
bedevere-bot
commented
Jan 17, 2025
|
bedevere-bot
commented
Jan 17, 2025
|
bedevere-bot
commented
Jan 17, 2025
|
Re: the buildbot failures, they're happening because the newly added heaptype inherits from object and does not have the |
Yhg1s
commented
Jan 17, 2025
#128951 should fix the buildbot failures. (This wasn't picked up by GHA because we apparently have no GHA that runs the tests in a single process/sequentially.) |
…8925) In the free threading build, the per thread reference counting uses a unique id for some objects to index into the local reference count table. Use 0 instead of -1 to indicate that the id is not assigned. This avoids bugs where zero-initialized heap type objects look like they have a unique id assigned.
In the free threading build, the per thread reference counting uses a unique id for some objects to index into the local reference count table. Use 0 instead of -1 to indicate that the id is not assigned. This avoids bugs where zero-initialized heap type objects look like they have a unique id assigned.