OpenWebUI/docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs synced 2025-05-19 02:42:15 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #226 from sebdanielsson/potential-oom-error

Browse Source 
Add tips for solving out-of-memory issues
This commit is contained in:
Timothy Jaeryang Baek 2024-09-25 22:37:39 +02:00 committed by GitHub
commit 6b41db6a26
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/getting-started/development.mdx
View File

@ -182,4 +182,18 @@ This setup involves mounting the `pipelines` directory to ensure any changes ref
This configuration uses volume bind-mounts. Learn more about how they differ from named volumes [here](https://docs.docker.com/storage/bind-mounts/).
:::
Through these setup steps, both new and experienced contributors can seamlessly integrate into the development workflow of Open WebUI. Happy coding! 🎉
## 🐛 Troubleshooting
### FATAL ERROR: Reached heap limit
When you encounter a memory-related error during the Docker build process—especially while executing `npm run build`—it typically indicates that the JavaScript heap has exceeded its memory limit. One effective solution is to increase the memory allocated to Node.js by adjusting the `NODE_OPTIONS` environment variable. This allows you to set a higher maximum heap size, which can help prevent out-of-memory errors during the build process. If you encounter this issue, try to allocate at least 4 GB of RAM, or higher if you have enough RAM.
You can increase the memory allocated to Node.js by adding the following line just before `npm run build` in the `Dockerfile`.
```docker title=/Dockerfile
ENV NODE_OPTIONS=--max-old-space-size=4096
```
---
Through these setup steps, both new and experienced contributors can seamlessly integrate into the development workflow of Open WebUI. Happy coding! 🎉