-
-
Notifications
You must be signed in to change notification settings - Fork 971
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
render() (really pandoc) can hang under certain circumstances #31
Comments
Thanks for reporting this. What a bug! I've made this change to ensure that we never hit this when calling pandoc from rmarkdown: |
Turns out there are a couple of other environment variables worth checking:
|
See Jeff's example here: https://gist.github.com/jjallaire/9390e6dfab153759423f |
Ensure that LANG and HOME are both set before running Pandoc, as their absence can cause fatal errors as discussed in rstudio#31.
Ensure that LANG and HOME are both set before running Pandoc, as their absence can cause fatal errors as discussed in rstudio#31.
…ersion' to freak out.
bug:#31: LC_CTYPE environment variable also causes 'pandoc --version' to freak out
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary. |
This is not a bug in rmarkdown. I report it here because it manifests itself by hanging rmarkdown::render() so there should be a record of what is really going on.
render() tries to establish the version of pandoc available. During this process 'pandoc --version' can hang forever (while using up all available memory) which causes render() to also hang forever.
I noticed this when trying to run render() in an ESS session running R on a remote server using tramp mode. The environment on the remote ubuntu system apparently sets LC_ALL=C as part of it's localization. As far as I can tell, on a ubuntu machine if the LC_ALL environment variable is set (to anything at all), the statically linked version of pandoc will hang.
This situation sounds exactly like (this bug)[https://ghc.haskell.org/trac/ghc/ticket/7344] reported 17 months ago.
Symptoms are 'pandoc --version' hangs and consumes memory until the process eventually dies with an OOM error. This seems to only happen when LC_ALL is set in the environment, and only when running the statically linked pandoc.
Note this problem does not occur if I run an older dynamically linked pandoc under the same circumstances.
The text was updated successfully, but these errors were encountered: