Closed tjmahr closed 4 years ago
Thanks for reporting this. I can't replicate this segfault on my Mac, so I wonder if this is platform specific (looks like you're on Windows). Does this only happen for you when you run it through the command line?
Yup, Windows 10.
I first got the problem in RStudio, but in that case, I would see RStudio session-crash window with the bomb, so I decided to test it on the command line to rule out RStudio.
I also tried again after reinstalling rstan, rstanarm, rstantools, and shinystan (edit: and bayesplot) from CRAN (just in case I had accidentally compiled the binaries myself during the last update). Still no luck.
Ok hmm, gonna need to get one of the devs with Windows to see if they can reproduce this.
@bgoodri when you have a sec can you see if you can reproduce this on your Windows machine?
On Mon, May 22, 2017 at 12:05 PM TJ Mahr notifications@github.com wrote:
Yup, Windows 10.
I first got the problem in RStudio, but in that case, I would see RStudio session-crash window with the bomb, so I decided to test it on the command line to rule out RStudio.
I also tried again after reinstalling rstan, rstanarm, rstantools, and shinystan from CRAN (just in case I had accidentally compiled the binaries myself during the last update). Still no luck.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/stan-dev/shinystan/issues/149#issuecomment-303144867, or mute the thread https://github.com/notifications/unsubscribe-auth/AHb4Q6T3sB0Vcik8ZS-zyn0hseCdR5vEks5r8bI3gaJpZM4Nig9f .
It works fine on my Windows 7 machine (of course :confused:). I'll have to try it on my other Windows 10 machine. later.
We are currently working on version 3.0 and hopefully this error will not occur anymore. Because of the new version we are currently closing old issues as a clean-up for version 3.0 such that we have a new overview of current open issues. If the issue persist is the new version please do let us know.
Best, Duco
I run the following from the command line:
I click on diagnostics. Window goes dim because of a shiny disconnect, and the command line session prints
Segmentation fault
and stops.This is what gets printed to the text file.
Edit: Updated so that command uses
--vanilla
flag for maximum reproducibility.