-
Notifications
You must be signed in to change notification settings - Fork 57
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
Apparent segfault in immutables.Map.__init__ #7
Comments
More details: this seems to happen consistently with CPython 3.6.1 or 3.6.2 on MacOS, but not earlier or later 3.6.x versions, and not on Linux at all: https://travis-ci.org/python-trio/trio/builds/409675722 Of course, it looks like some weird memory corruption thing, so it's possible the bug is latent in other configurations and those are just the builds where it happens to trigger a segfault. But useful for reproducing, maybe. I also managed to get a traceback out:
|
Travis MacOS is much more functional than it used to be, and on ci.cryptography.org we're hitting: MagicStack/immutables#7 So let's try turning on Travis's MacOS and see how it goes, while scaling back our Jenkins testing so that bug doesn't block everything.
I think the bug is already fixed in immutables, i just need to bump the dep. Can you try to install the latest immutables and see if the bug is still there? |
Forcing a |
While the Travis MacOS infrastructure is clearly *much* better than it used to be, doing these tests on Jenkins is still faster overall, and it avoids hitting python-triogh-584. This commit: - adds a temporary workaround for MagicStack/immutables#7 - re-enables all MacOS builds on Jenkins - including 3.7, which was previously not enabled - re-disables Travis MacOS builds
I've released contextvars 2.3 that use the fixed immutables package. Closing this now. |
The latest release of contextvars (v2.3) fixed this bug, so we don't need a workaround anymore: MagicStack/immutables#7
Thanks! |
We're getting an intermittent segfault in the
contextvars
library, on our MacOS CI: https://ci.cryptography.io/blue/rest/organizations/jenkins/pipelines/python-trio/pipelines/trio/branches/PR-575/runs/2/nodes/6/steps/33/log/?start=0The crash-handler traceback shows it as happening on line 27 of
contextvars/__init__.py
, which seems to be:So our current hypothesis is that
immutables.Map()
sometimes segfaults? Does that ring any bells?We don't know how to reproduce it locally, but I believe that's the python.org build of 3.6.1.
Previous discussion: python-trio/trio#200 (comment)
The text was updated successfully, but these errors were encountered: