-
Notifications
You must be signed in to change notification settings - Fork 28
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
Q() segfaults on Windows & Linux with multiprocess scheduler with clustermq 0.9.0 #308
Comments
Seems to be related to shutdown of workers given that it always happens after all jobs have completed. Also, can provoke this with LSF (but it is harder to reproduce, needs Q() in a loop) |
@mschubert are you able to reproduce this as well? |
Yes: I can (occasionally) reproduce, and I'll try to track it down as soon as possible. I'm also happy to report that I've got internet again at the place I moved to 😅 |
@luwidmer Can you check if it still occurs with the current git version? remotes::install_github("mschubert/clustermq@master") |
Unfortunately yes (I modified the version number in DESCRIPTION to be 0.9.0.12345 and that version indeed got loaded) |
I fixed another bug in 5612364, which may be the cause of this crash as well. Can you confirm if this now works? (same git install command as above) |
I just really tried to provoke it with 1000s of Q() calls, that seems to have done it, superb @mschubert ! Might make sense to push this as 0.9.1 if no other big issues pop up? |
Great, thanks! Yes, plan is to push |
I also get segfaults with the following even simpler Q() example (simpler than #306), both on Linux and Windows:
On Linux with R 4.1.0, this results in
On Windows with R 4.3.0 this results in the same error as for @wlandau's example in #306:
The text was updated successfully, but these errors were encountered: