Skip to content

fix: temporarily cap PySide6 below 6.12 - #4

Merged
lukisch merged 8 commits into
masterfrom
diagnose/prosync-qt-lifecycle-crash-20261012
Oct 12, 2026
Merged

lukisch merged 8 commits into
masterfrom
diagnose/prosync-qt-lifecycle-crash-20261012

Conversation

@lukisch

@lukisch lukisch commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

A controlled Linux/Python 3.10 A/B run with identical non-Qt dependencies showed:

  • PySide6/Shiboken6 6.11.2: standalone SFTP exited 0; pytest passed 9/9.
  • PySide6/Shiboken6 6.12.0: standalone SFTP printed success, then aborted with munmap_chunk(): invalid pointer (exit -6); pytest still passed 9/9.

This supports a temporary compatibility bound for the measured SFTP process path. It does not identify the native memory-corruption writer or claim a runtime fix. Package metadata and both CI install paths now use PySide6>=6.5.0,<6.12. The regular smoke and full test suites remain; one-off diagnostic steps were removed while faulthandler and actual child exit reporting remain. Version 3.2.0 is unchanged.

Reconsider the bound only after a newer Qt release passes the unchanged standalone SFTP test, the complete smoke runner, and the existing full CI matrices.

@github-actions

Copy link
Copy Markdown

Welcome! 👋 Thanks for your first pull request in this repository.

A maintainer will review it soon. Please make sure:

  • Your changes are tested
  • Documentation is updated if needed
  • The PR description explains what and why

Thanks for contributing!

@lukisch lukisch changed the title ci: expose Qt test process crash diagnostics fix: temporarily cap PySide6 below 6.12 Oct 12, 2026
@lukisch
lukisch merged commit 464bbf8 into master Oct 12, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant