github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-22 09:31:58 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[PR #7710] [CLOSED] fix: prevent out-of-memory errors in make update #109407

New Issue
Closed
opened 2026-05-18 08:46:14 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-18 08:46:14 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/7710
Author: @bernadinm
Created: 12/9/2024
Status: ❌ Closed

Base: main ← Head: fix/make_update

📝 Commits (2)

  • 2d5a7cf fix: chmod by default update_ollama_models
  • da85f2f fix: set proper max-old-space-size for make update

📊 Changes

2 files changed (+1 additions, -0 deletions)

View changed files

📝 Dockerfile (+1 -0)
📝 update_ollama_models.sh (+0 -0)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

  • Target branch: The pull request targets the main branch.
  • Description: A concise description of the changes made in this pull request is provided below.
  • Changelog: A changelog entry is provided below.
  • Documentation: The relevant documentation has been updated.
  • Dependencies: There are no new dependencies.
  • Testing: Manually verified that the make update command no longer runs out of memory during the build process after applying the changes.
  • Code review: A self-review of the code has been performed, addressing any coding standard issues and ensuring adherence to the project's coding standards.
  • Prefix: The pull request title is prefixed with fix.

Changelog Entry

Description

This pull request fixes the issue with the make update command running out of memory during the build process. The max-old-space-size is increased to 4096 to prevent out-of-memory errors.

Added

  • Increased the max-old-space-size to 4096 in the Dockerfile.
  • Added execute permissions to the update_ollama_models.sh script.

Changed

  • Updated the Dockerfile to include the increased max-old-space-size.

Deprecated

  • None

Removed

  • None

Fixed

  • The issue with the make update command running out of memory during the build process.

Security

  • None

Breaking Changes

  • None

Additional Information

This pull request aims to resolve the issue with the make update command running out of memory during the build process. The changes include increasing the max-old-space-size to 4096 and adding execute permissions to the update_ollama_models.sh script. Verified that the changes fix the issue by manually running the make update command and observing the results.

Screenshots or Videos

Here are the relevant logs:

22.18 [plugin:vite:resolve] [plugin vite:resolve] Module "node:child_process" has been externalized for browser compatibility, imported by "/app/node_modules/pyodide/pyodide.mjs". See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
22.18 [plugin:vite:resolve] [plugin vite:resolve] Module "node:path" has been externalized for browser compatibility, imported by "/app/node_modules/pyodide/pyodide.mjs". See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
22.18 [plugin:vite:resolve] [plugin vite:resolve] Module "node:url" has been externalized for browser compatibility, imported by "/app/node_modules/pyodide/pyodide.mjs". See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
23.17 node_modules/onnxruntime-web/dist/ort.bundle.min.mjs (6:96500): Use of eval in "node_modules/onnxruntime-web/dist/ort.bundle.min.mjs" is strongly discouraged as it poses security risks and may cause issues with minification.
35.31 ✓ 3537 modules transformed.
36.07
36.07 <--- Last few GCs --->
36.07
36.07 [17:0xffffb7cc0000]    29232 ms: Scavenge 2005.3 (2084.4) -> 1998.8 (2085.7) MB, pooled: 0 MB, 1.82 / 0.00 ms  (average mu = 0.913, current mu = 0.934) allocation failure;
36.07 [17:0xffffb7cc0000]    29247 ms: Scavenge 2006.2 (2085.7) -> 1999.9 (2101.7) MB, pooled: 0 MB, 3.51 / 0.00 ms  (average mu = 0.913, current mu = 0.934) allocation failure;
36.07
36.07
36.07 <--- JS stacktrace --->
36.07
36.07 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
36.07 ----- Native stack trace -----
36.07
36.65 npm error path /app
36.65 npm error command failed
36.65 npm error signal SIGABRT
36.65 npm error command sh -c npm run pyodide:fetch && vite build
36.66 npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-09T06_59_27_596Z-debug-0.log
------
failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 1
make: *** [update] Error 17

These logs show the error that was encountered before making the changes, and the successful build after applying the changes.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/7710 **Author:** [@bernadinm](https://github.com/bernadinm) **Created:** 12/9/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/make_update` --- ### 📝 Commits (2) - [`2d5a7cf`](https://github.com/open-webui/open-webui/commit/2d5a7cfb503a85fafeaf73246278f0f936e6f31b) fix: chmod by default update_ollama_models - [`da85f2f`](https://github.com/open-webui/open-webui/commit/da85f2fbdcf52bc54cc2c6b387e3c1687004c723) fix: set proper max-old-space-size for make update ### 📊 Changes **2 files changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `Dockerfile` (+1 -0) 📝 `update_ollama_models.sh` (+0 -0) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** The pull request targets the `main` branch. - [x] **Description:** A concise description of the changes made in this pull request is provided below. - [x] **Changelog:** A changelog entry is provided below. - [x] **Documentation:** The relevant documentation has been updated. - [x] **Dependencies:** There are no new dependencies. - [x] **Testing:** Manually verified that the `make update` command no longer runs out of memory during the build process after applying the changes. - [x] **Code review:** A self-review of the code has been performed, addressing any coding standard issues and ensuring adherence to the project's coding standards. - [x] **Prefix:** The pull request title is prefixed with `fix`. # Changelog Entry ### Description This pull request fixes the issue with the `make update` command running out of memory during the build process. The `max-old-space-size` is increased to 4096 to prevent out-of-memory errors. ### Added - Increased the `max-old-space-size` to 4096 in the Dockerfile. - Added execute permissions to the `update_ollama_models.sh` script. ### Changed - Updated the Dockerfile to include the increased `max-old-space-size`. ### Deprecated - None ### Removed - None ### Fixed - The issue with the `make update` command running out of memory during the build process. ### Security - None ### Breaking Changes - None --- ### Additional Information This pull request aims to resolve the issue with the `make update` command running out of memory during the build process. The changes include increasing the `max-old-space-size` to 4096 and adding execute permissions to the `update_ollama_models.sh` script. Verified that the changes fix the issue by manually running the `make update` command and observing the results. ### Screenshots or Videos Here are the relevant logs: ``` 22.18 [plugin:vite:resolve] [plugin vite:resolve] Module "node:child_process" has been externalized for browser compatibility, imported by "/app/node_modules/pyodide/pyodide.mjs". See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details. 22.18 [plugin:vite:resolve] [plugin vite:resolve] Module "node:path" has been externalized for browser compatibility, imported by "/app/node_modules/pyodide/pyodide.mjs". See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details. 22.18 [plugin:vite:resolve] [plugin vite:resolve] Module "node:url" has been externalized for browser compatibility, imported by "/app/node_modules/pyodide/pyodide.mjs". See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details. 23.17 node_modules/onnxruntime-web/dist/ort.bundle.min.mjs (6:96500): Use of eval in "node_modules/onnxruntime-web/dist/ort.bundle.min.mjs" is strongly discouraged as it poses security risks and may cause issues with minification. 35.31 ✓ 3537 modules transformed. 36.07 36.07 <--- Last few GCs ---> 36.07 36.07 [17:0xffffb7cc0000] 29232 ms: Scavenge 2005.3 (2084.4) -> 1998.8 (2085.7) MB, pooled: 0 MB, 1.82 / 0.00 ms (average mu = 0.913, current mu = 0.934) allocation failure; 36.07 [17:0xffffb7cc0000] 29247 ms: Scavenge 2006.2 (2085.7) -> 1999.9 (2101.7) MB, pooled: 0 MB, 3.51 / 0.00 ms (average mu = 0.913, current mu = 0.934) allocation failure; 36.07 36.07 36.07 <--- JS stacktrace ---> 36.07 36.07 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 36.07 ----- Native stack trace ----- 36.07 36.65 npm error path /app 36.65 npm error command failed 36.65 npm error signal SIGABRT 36.65 npm error command sh -c npm run pyodide:fetch && vite build 36.66 npm error A complete log of this run can be found in: /root/.npm/_logs/2024-12-09T06_59_27_596Z-debug-0.log ------ failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 1 make: *** [update] Error 17 ``` These logs show the error that was encountered before making the changes, and the successful build after applying the changes. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-18 08:46:14 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#109407
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?