-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Assertion Failure: Deepfrozen code object gets re-quickened #92031
Comments
Replicated on linux (WSL). |
test_repeated_init_exec is here: https://github.com/python/cpython/blob/main/Programs/_testembed.c#L167-L177 Replacing the assertion with
Sometimes the opcode in question changes, but it seems to always be in I wonder if this has something to do with frozen modules keeping old code objects around between interpreter setup/teardown? @ericsnowcurrently or @vstinner or @markshannon any ideas? |
Solutions I could think of:
|
This also makes me wonder if we should have some sort weekly buildbot run the tests with |
I think this is the reason for some intermittent Windows buildbot failures. |
It might be worth checking before the fix whether the reproducers go well with the buildbots. |
@neonene Azure pipelines Ubuntu PR tests failed at #92130 on It would be better to pin down a more deterministic (and faster-running) reproducer. I'm not super familiar with the importlib implementation, but the key should just be to exercise |
I saw the test at |
Recent failure on s390x RHEL8 Refleaks 3.x (reformatted manually): https://buildbot.python.org/all/#/builders/75/builds/385
|
I think that restoring the code to its initial state during @gvanrossum any thoughts? |
I think this should be handled in |
@sweeneyde Can this be closed now that GH-92031 is fixed? |
Fixed by b156578 |
…pythonGH-92440) (cherry picked from commit 27185f9) Co-authored-by: Dennis Sweeney <[email protected]>
…2440) (cherry picked from commit 27185f9) Co-authored-by: Dennis Sweeney <[email protected]>
A third bug found while working on #91713 🙃
Bug report
I can reproduce this locally on my Windows machine:
This is the result:
A more self-contained simplified (less unittest) reproducer is this:
This fails with the following message:
The text was updated successfully, but these errors were encountered: