-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Seems to have a memory leek #19824
Comments
Reverting nuxt to 3.2.3 and Docus to 1.9.0 works well. |
Could you try with Docus 1.9.9 and Nuxt 3.2.3 @Barbapapazes ? I am quite sure it does not come from Docus but want to be 100% sure |
With Docus 1.9.0 and Nuxt 3.3.1, max RAM usage at 3.5Go Use the build command in my armonik-docs-theme repo on windows. (yes, 3.5Go for each run) Using GitHub Runner, |
This might be linked to #19783, which is caused by an upstream issue in rollup. Would you try pinning rollup to 3.18.0? |
It works with rollup 3.18.0 https://github.com/esoubiran-aneo/armonik-docs-theme-1/actions/runs/4471070531/jobs/7855462227 @danielroe |
Great. Let's follow in the issue I linked then. |
Environment
Windows_NT
v18.12.1
3.3.1
2.3.1
pnpm@7.29.0
vite
app
,extends
-
-
Reproduction
A normal repo https://github.com/aneoconsulting/ArmoniK.Admin.GUI/tree/main/.docs
The working CI https://github.com/aneoconsulting/ArmoniK.Admin.GUI/actions/workflows/deploy-docs.yml
A repo with potential memory leaks https://github.com/aneoconsulting/armonik-docs-theme
The broken CI https://github.com/aneoconsulting/armonik-docs-theme/actions/workflows/deploy-docs.yml
Describe the bug
Hello,
Since I update to Docus 1.9.9 and to Nuxt 3.3.1, I noticed a huge usage of ram.
With the normal repo, my computer use up to 1.5Go of RAM but with the broken repo, I use up to 3Go (and the GitHub runner failed). Not sure if it come from Nuxt or from Docus. I will continue to investigate but I will be unable to resolve this.
Thanks
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: