Bump dart_bridge to 1.9.0 - #41
Merged
Merged
Conversation
dart_bridge 1.9.0 adds serious_python_hard_exit, which terminates the process without running atexit handlers or C++ static destructors. Embedders were seeing a SIGSEGV on exit: the interpreter runs on a detached thread that may still be executing native extension code when the host quits, and a normal exit() runs __cxa_finalize, destroying the C++ statics inside every loaded extension module out from under it. The reported case died in matplotlib's ft2font looking up a pybind11 type-caster map that had just been destructed. No Python versions change. This re-release exists to publish the updated manifest so serious_python can regenerate its version tables against it. See flet-dev/dart-bridge#20.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps
manifest.jsontodart_bridge1.9.0. No Python versions change.Why
dart_bridge 1.9.0 adds
serious_python_hard_exit, which terminates the process without runningatexithandlers or C++ static destructors (flet-dev/dart-bridge#20).Embedders were seeing a
SIGSEGVon exit from apps that had otherwise finished their work. The interpreter runs on a detached thread that may still be executing native extension code when the host quits, and a normalexit()runs__cxa_finalize, destroying the C++ statics inside every loaded extension module out from under it. The reported case died in matplotlib'sft2fontlooking up a pybind11 type-caster map that had just been destructed;numpy,Pillowand Flutter's own Skia statics are torn down by the same pass.Release chain
manifest.jsonis the single source of truth and is published as a release asset, so a re-release is what actually propagates the new bridge version:Build Python Packagesrun with arelease_dateto cut the dated releasedart run serious_python:gen_version_tables --release-date <YYYYMMDD>), which is what movesdart_bridge_versionandpython_build_release_datein the generatedpython_versions.properties/python_versions.dartserious_pythonpinNothing downstream can move until the release in step 2 exists, since the generator fetches the manifest from the python-build release by date.