-
Notifications
You must be signed in to change notification settings - Fork 591
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
[BUG-REPORT] vaex causes a segmentation fault on windows #2442
Comments
potentially a memory leak specific to windows: |
I wonder if we should use the same wheel we build for releasing in the testing. |
cibuildwheel has built-in support to run pytest on built wheels right after building them https://cibuildwheel.pypa.io/en/stable/options/#testing |
@maartenbreddels @ddelange : Sorry to bother you but curious when a fix with this might roll out? Maybe a version that skips Windows temporarily might be easier? |
Bump... Any idea when this might be resolved? It has been >a month since the last version was yanked. Maybe it makes sense to release without Windows support in the meanwhile? |
from my side it's not clear what would be the fix |
Description
We're seeing a
Windows fatal exception: access violation
runningvaex-core
4.18.1 on windows with Python 3.9, not sure if the issue also affects other Python versions. I mentioned this in #2439 (comment), believing it to be related, but this issue persists withvaex-core
4.18.1, as can be see in this CI run.Software information
import vaex; vaex.__version__)
:vaex-core
4.18.1Additional information
The full stack trace is
Stack Trace
The text was updated successfully, but these errors were encountered: