Closed Unco3892 closed 8 months ago
The link you referred to is describing out-of-memory issues in Deno:
In this example, we’re setting the maximum amount of memory to be allocated by Deno to be 8GB.
You're running out of memory in R. That option won't work.
Thank you for your reply. You're right that this related to Deno (TypeScript) but I'm not sure what element of this interferes the my Quarto rendering that is causing this. As mentioned, even if this is related to Deno, setting this environment variable seems to handle the issue locally on similar computers with 16Gb of memory (ubuntu-latest
and windows-latest
) to the ones of GitHub actions (ubuntu-latest
), but when running in actions, it does not work. If it was a memory issue only caused by the code execution, it should not render locally either. I invite you to try rendering this locally on your hardware to verify.
You're right that this related to Deno (TypeScript)
Sorry, but you misread my message. I said: "You're running out of memory in R." The option you've unsuccessfully used controls memory usage in Deno. That's not what the problem is. The problem is that you're running out of memory in R.
Thank you again for your answer. Adding the following run to .github/workflows/publish.yml
resolved the issue:
- name: Increase RAM limit for R
run: |
ulimit -s 16384
ulimit -a #confirm the limit increase
Hi,
I have a Quarto website for a course here https://github.com/do-unil/mlba which runs fine locally and when you have
_freeze
directory with GitHub actions. However, when removing the_freeze
directory from the repo for a clean rendering with GitHub actions, I get the following error https://github.com/do-unil/mlba/actions/runs/8005417025/job/21864790141#step:7:648 . I tried modifying the.github/workflows/.publish.yml
that occurs often for Quarto here https://quarto.org/docs/troubleshooting/index.html#out-of-memory-issues, setting the environment variable with export before the Quarto installation but no success.I then thought this may be a more general R memory limit issue by looking at the solutions https://stackoverflow.com/questions/14719349/error-c-stack-usage-is-too-close-to-the-limit and https://community.rstudio.com/t/error-c-stack-usage-7974692-is-too-close-to-the-limit-with/90465, I tried also modifying the
publish.yml
according to that but still no success:Any idea how to resolve this and perhaps better document it? Thank you in advance for your help.