-
Notifications
You must be signed in to change notification settings - Fork 96
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
Occasional segfaults with image editor #1815
Comments
I thought this was related to #1810, but it hasn't been merged yet. Not sure that the changes there will fix these errors, though. |
But it is likely related to #1807. |
This may not be resolved - still seeing this in PRs after this has been merged, although the PRs didn't directly include this. |
Re-opening - this is still happening. |
Hypothesis: this may be related to https://stackoverflow.com/questions/15021877/pyqt-showing-a-file-dialog-after-creating-a-pixmap-produces-a-segmentation-faul as we are going from array (copied) -> QImage -> QPixmap and nothing is keeping the QImage alive (or the array bytes it references). As a result, this may be a Pyface bug. Still haven't reproduced. |
This looks like a Pyface issue with a straightforward fix. See enthought/pyface#1108 and enthought/pyface#1109. I will leave this open until those are merged. |
The Pyface issue is dealt with and a new release has been made. Closing this issue. If we continue to see issues after this we will re-open. |
Looks like the failure is always Windows, Python 3.6, PySide2.
The text was updated successfully, but these errors were encountered: