-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
Various hard to track / repeat crashes on different machines with stanheaders 2.26.26/27 #1080
Comments
Is this both rstan and StanHeaders 2.26, or rstan 2.21 and StanHeaders 2.26? Can you share a reproducible example? |
I'm not sure if it is with rstan 2.26, will have to check.
|
If you reinstall rstan 2.21 from source does it still crash? |
I think @ssp3nc3r and others have also been dealing with crashes on Mac using the latest CRAN versions of R, RStan and StanHeaders |
If they can share a reproducible example than I can debug locally on Mac. I can't reproduce the ctsem crash above on Mac unfortunately |
I think for @ssp3nc3r every Stan program was crashing, is that right Scott? |
Hee’s another report of crashing on a Mac with the latest CRAN versions of everything: https://discourse.mc-stan.org/t/example-in-rstan-sampling-crashes-r-completely-on-mac-osx/27873/3 Unfortunately no Stan programs provided, but sounds like it was happening for every program like in @ssp3nc3r’s case |
I'm also seeing now that the only setup passing tests when building and testing ctsem on github actions is the one that upgrades to rstan 2.26 . https://github.com/cdriveraus/ctsem/actions/runs/5455364042/jobs/9926706393 but still getting complete pc freezing when running for longer periods using bigIRT, with rstan 2.26... |
The tricky thing with 2.26 is that rstan 2.21 needs to be rebuilt against StanHeaders 2.26, otherwise it will segfault. Additionally 2.26 has a lot of custom @bgoodri what do you think? I think it would be best to get 2.32 up as soon as possible and be debugging/troubleshooting that, rather than debugging/troubleshooting 2.21/2.26 with issues that might not even be present with the newer version |
I agree
…On Thu, Jul 6, 2023 at 5:35 AM Andrew Johnson ***@***.***> wrote:
The tricky thing with 2.26 is that rstan 2.21 needs to be rebuilt against
StanHeaders 2.26, otherwise it will segfault. Additionally 2.26 has a lot
of custom IFDEFs and branching for compatibility, so things are likely to
be much more stable once 2.32 is up.
@bgoodri <https://github.com/bgoodri> what do you think? I think it would
be best to get 2.32 up as soon as possible and be debugging/troubleshooting
that, rather than debugging/troubleshooting 2.21/2.26 with issues that
might not even be present with the newer version
—
Reply to this email directly, view it on GitHub
<#1080 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZ2XKR7FHEE4DREAMUFME3XO2BEJANCNFSM6AAAAAAZ7E2Z6M>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I am seeing issues on different pc's, operating systems, and software packages, ranging from complete freezing to weird errors compiling to rstudio sessions crashing, using R 4.2 / 4.3 . Specifically, software packages bigIRT and ctsem, which both use rstan for computing the log probability / gradient of fairly large stan models, and sometimes use the sampling procedure. Sorry for the terribly vague report I am trying to track the occurrences to make sense of them and trying to make sense of users reports, but I wanted to post something about it -- is there some awareness of the issues, are others facing similar problems?
As best as I can tell the problems started with 2.26.26 , but maybe some were there already with .25 I can't be sure.
Sometimes the issues only happen after analyzing data for a day, in other cases the crash is repeatable (for the specific machine / os / R version configuration) and happens quickly.
The text was updated successfully, but these errors were encountered: