1.120.7无法build：JavaScript heap out of memory

[yincangshiwei]

📦 部署环境

Docker

📦 部署模式

服务端模式(lobe-chat-database 镜像)

📌 软件版本

1.120.7

💻 系统环境

Other Linux

🌐 浏览器

Other, Chrome

🐛 问题描述

这几天更新都对硬件要求贼高，现在这版怎么调都无法调。

0.303
0.303 > @lobehub/[email protected] build:docker
0.303 > npm run prebuild && DOCKER=true next build && npm run build-sitemap
0.303
0.452
0.452 > @lobehub/[email protected] prebuild
0.452 > tsx scripts/prebuild.mts
0.452
0.779 [[email protected]] injecting env (0) from .env -- tip: ⚙️ enable debug logging with { debug: true }
0.779 Starting prebuild cleanup...
0.782 ♻️ Removed src/app/desktop successfully
0.786 ♻️ Removed src/app/(backend)/trpc/desktop successfully
0.786 Prebuild cleanup completed.
2.034 Attention: Next.js now collects completely anonymous telemetry regarding usage.
2.034 This information is used to shape Next.js' roadmap and prioritize features.
2.034 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
2.034 https://nextjs.org/telemetry
2.034
2.162 ▲ Next.js 15.3.5
2.162 - Experiments (use with caution):
2.162 ⨯ serverMinification
2.162
2.225 Creating an optimized production build ...
2.741 ○ (serwist) The service worker will not be automatically registered, please call 'window.serwist.register()' in 'componentDidMount' or 'useEffect'.
2.747 ✓ (serwist) Bundling the service worker script with the URL '/sw.js' and the scope '/'...
317.8 [webpack.cache.PackFileCacheStrategy] Serializing big strings (172kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
317.8 [webpack.cache.PackFileCacheStrategy] Serializing big strings (128kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
545.1
545.1 <--- Last few GCs --->
545.1
545.1 [65:0x7daa000] 541909 ms: Mark-Compact 3912.1 (4127.4) -> 3867.7 (4099.3) MB, pooled: 16 MB, 2299.06 / 0.00 ms (average mu = 0.192, current mu = 0.143) allocation failure; scavenge might not succeed
545.1 [65:0x7daa000] 544263 ms: Mark-Compact 3933.1 (4154.1) -> 3886.1 (4113.8) MB, pooled: 20 MB, 2109.36 / 0.00 ms (average mu = 0.154, current mu = 0.104) allocation failure; GC in old space requested
545.1
545.1
545.1 <--- JS stacktrace --->
545.1
545.1 FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
545.1 ----- Native stack trace -----
545.1
545.1 1: 0xe1803a node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
545.1 2: 0x11ec9c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
545.1 3: 0x11ecc97 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
545.1 4: 0x141a575 [node]
545.1 5: 0x141a5a3 [node]
545.1 6: 0x143367a [node]
545.1 7: 0x1436848 [node]
545.1 8: 0x1c9c351 [node]
550.5 Aborted (core dumped)

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

👀 @yincangshiwei

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

你的构建失败是因为内存不足，近期版本（如 1.118.8 及以后）Docker 构建至少需要 16GB 内存，8GB 已无法满足需求，主要是 Next.js 构建和静态资源预加载导致内存占用大幅提升 参考。

解决方法：

1. 增加物理/虚拟机内存到 16GB 以上。

2. 构建时设置环境变量提升 Node.js 最大堆内存，例如：

   NODE_OPTIONS="--max-old-space-size=8192" npm run build:docker
   

   或在 Dockerfile/build 命令里加上 NODE_OPTIONS，分配 8GB 或更高（如 16384）。

3. 如果用 docker-compose，可以在服务配置里加上内存限制，例如：

   deploy:
     resources:
       limits:
         memory: 16G

   或运行容器时加 --memory=16g。

目前没有发现近期有 pull request 或代码变更进一步提升了内存需求，主要还是 Next.js 及静态资源导致的构建瓶颈 参考。

低于 16GB 内存基本无法顺利构建新版镜像，建议升级硬件或用云端构建后拉取镜像。

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Zhouguanyang]

@dosu 1.120.1也是同样的问题，--max-old-space-size=12488都没用。你们自己镜像是不是也构建失败了？以往版本发布十几分钟就发了。