-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Rstudio crashes when starting shinyApp incl. renderPlot() #1726
Comments
If you have recently upgrade to R 3.4.0, this is likely because you have an old version of the Cairo package that is causing the process to crash. Please read this: Can you include the output of |
Thanks for the fast reply! The output of setting value Packages ---------------------------------------------------------------------------------------------------------------------------- |
I think you will need to reinstall most of your packages under R 3.4.0. Please read the document that I linked to above, in particular the sections "Detecting which version of R a package was built with" and "Reinstalling packages with the new version of R". |
That solved it, thanks. I had troubles installing any packages, but after solving that, the mentioned |
Short:
Rstudio crashes when I start a shinyApp that has a
renderPlot()
+plotOutput
in it.Running it in Chrome the console gives me:
Uncaught TypeError: Cannot read property 'readyState' of null
(shiny.min.js:3)Example:
I open RStudio and create a new app:
RStudio -> File -> New File ->Shiny Web App
which gives me the standard "Old Faithful Geyser Data" app.
If I comment out
plotOutput("distPlot")
and run the app everything is fine.However, if i run the app including
plotOutput("distPlot")
, I get:R Session aborted - R encountered a fatal error,...
Technical details.
I am using RStudio 1.0.1.4.3 and shiny 1.0.3.
I removed and reinstalled RStudio as well as shiny.
(It happened when I ran an app from a SO question i wanted to answer, so it might have been that
i installed some packages prior to that, if that could possibly have any impact)
The text was updated successfully, but these errors were encountered: