部署“react-admin”应用程序时，Heroku服务器崩溃，并显示“JavaScript堆内存不足”

ecbunoof  于 2022-11-13  发布在  React
关注(0)|答案(8)|浏览(119)

我目前正在使用“react-admin”开发一个管理面板，它在我的本地上运行良好，但当我将应用程序上传到Heroku时，构建失败，并出现以下错误：“严重错误：无效的标记压缩接近堆限制分配失败- JavaScript堆内存不足”
我已经将问题缩小到了初始的import { Admin } from 'react-admin';，方法是设置一个干净的项目，只使用“react-admin”包和一个简单的Admin导入。只要我尝试使用该组件，部署就会失败，并出现“heap out of memory”错误。
是否有其他人遇到过此问题？
这是我的包裹.json：

{
  "name": "mrewards_admin",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "axios": "^0.19.0",
    "deepmerge": "^4.2.2",
    "prop-types": "^15.7.2",
    "react": "^16.12.0",
    "react-admin": "^3.0.2",
    "react-dom": "^16.12.0",
    "react-scripts": "3.2.0"
  },
  "engines": {
    "node": "13.0.1"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

下面是Heroku日志的输出：

2019-12-06T00:29:07.000000+00:00 app[api]: Build succeeded
2019-12-06T00:29:10.340460+00:00 heroku[web.1]: State changed from starting to up
2019-12-06T00:29:10.135608+00:00 app[web.1]: ℹ ｢wds｣: Project is running at http://172.18.103.22/
2019-12-06T00:29:10.135999+00:00 app[web.1]: ℹ ｢wds｣: webpack output is served from /
2019-12-06T00:29:10.136098+00:00 app[web.1]: ℹ ｢wds｣: Content not from webpack is served from /app/public
2019-12-06T00:29:10.136196+00:00 app[web.1]: ℹ ｢wds｣: 404s will fallback to /index.html
2019-12-06T00:29:10.136405+00:00 app[web.1]: Starting the development server...
2019-12-06T00:29:10.136409+00:00 app[web.1]:
2019-12-06T00:30:46.302146+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=test-react-admin.herokuapp.com request_id=b7cafb3a-311c-4ef2-bd61-cb1f863e69ca fwd="216.81.49.130" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0 protocol=https
2019-12-06T00:30:47.234363+00:00 app[web.1]:
2019-12-06T00:30:47.234390+00:00 app[web.1]: <--- Last few GCs --->
2019-12-06T00:30:47.234392+00:00 app[web.1]:
2019-12-06T00:30:47.234413+00:00 app[web.1]: [30:0x492c940]    98675 ms: Scavenge 240.7 (257.5) -> 239.8 (257.7) MB, 1.7 / 0.0 ms  (average mu = 0.238, current mu = 0.037) allocation failure
2019-12-06T00:30:47.234415+00:00 app[web.1]: [30:0x492c940]    98685 ms: Scavenge 240.7 (257.7) -> 239.9 (258.0) MB, 1.9 / 0.0 ms  (average mu = 0.238, current mu = 0.037) allocation failure
2019-12-06T00:30:47.234418+00:00 app[web.1]: [30:0x492c940]    98903 ms: Mark-sweep 240.8 (258.0) -> 237.9 (258.0) MB, 211.0 / 0.1 ms  (average mu = 0.350, current mu = 0.474) allocation failure scavenge might not succeed
2019-12-06T00:30:47.234419+00:00 app[web.1]:
2019-12-06T00:30:47.234421+00:00 app[web.1]:
2019-12-06T00:30:47.234422+00:00 app[web.1]: <--- JS stacktrace --->
2019-12-06T00:30:47.234423+00:00 app[web.1]:
2019-12-06T00:30:47.234426+00:00 app[web.1]: ==== JS stack trace =========================================
2019-12-06T00:30:47.234427+00:00 app[web.1]:
2019-12-06T00:30:47.234429+00:00 app[web.1]: 0: ExitFrame [pc: 0x1374fd9]
2019-12-06T00:30:47.234431+00:00 app[web.1]: Security context: 0x2a1cf61808a1 <JSObject>
2019-12-06T00:30:47.234433+00:00 app[web.1]: 1: _next2(aka _next2) [0x2546e8465cf9] [0x1b716e9004a9 <undefined>:~21] [pc=0x1d633e40a0e8](this=0x1b716e9004a9 <undefined>)
2019-12-06T00:30:47.234440+00:00 app[web.1]: 2: /* anonymous */(aka /* anonymous */) [0x2546e8465ea1] [0x1b716e9004a9 <undefined>:46] [bytecode=0x6238003a241 offset=37](this=0x1b716e9004a9 <undefined>,0x1b716e9004a9 <undefined>,0x1b716e9004a9 <undefined>)
2019-12-06T00:30:47.234441+00:00 app[web.1]: 3: _next1(aka _ne...
2019-12-06T00:30:47.234443+00:00 app[web.1]:
2019-12-06T00:30:47.234445+00:00 app[web.1]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
2019-12-06T00:30:47.234453+00:00 app[web.1]:
2019-12-06T00:30:47.245340+00:00 app[web.1]: Writing Node.js report to file: report.20191206.003047.30.0.001.json
2019-12-06T00:30:47.245345+00:00 app[web.1]: Node.js report completed
2019-12-06T00:30:47.245828+00:00 app[web.1]: 1: 0x9da7c0 node::Abort() [node]
2019-12-06T00:30:47.246377+00:00 app[web.1]: 2: 0x9db976 node::OnFatalError(char const*, char const*) [node]
2019-12-06T00:30:47.246963+00:00 app[web.1]: 3: 0xb39f1e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
2019-12-06T00:30:47.247418+00:00 app[web.1]: 4: 0xb3a299 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
2019-12-06T00:30:47.247992+00:00 app[web.1]: 5: 0xce5635  [node]
2019-12-06T00:30:47.248561+00:00 app[web.1]: 6: 0xce5cc6 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [node]
2019-12-06T00:30:47.249102+00:00 app[web.1]: 7: 0xcf1b5a v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
2019-12-06T00:30:47.249627+00:00 app[web.1]: 8: 0xcf2a65 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
2019-12-06T00:30:47.250190+00:00 app[web.1]: 9: 0xcf5478 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
2019-12-06T00:30:47.250701+00:00 app[web.1]: 10: 0xcbbda7 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType) [node]
2019-12-06T00:30:47.251301+00:00 app[web.1]: 11: 0xff1e0b v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
2019-12-06T00:30:47.251959+00:00 app[web.1]: 12: 0x1374fd9  [node]
2019-12-06T00:30:47.285408+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2019-12-06T00:30:47.285920+00:00 app[web.1]: npm ERR! errno 1
2019-12-06T00:30:47.287473+00:00 app[web.1]: npm ERR! ra-test@0.1.0 start: `react-scripts start`
2019-12-06T00:30:47.287759+00:00 app[web.1]: npm ERR! Exit status 1
2019-12-06T00:30:47.288057+00:00 app[web.1]: npm ERR!
2019-12-06T00:30:47.288300+00:00 app[web.1]: npm ERR! Failed at the ra-test@0.1.0 start script.
2019-12-06T00:30:47.288528+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2019-12-06T00:30:47.295555+00:00 app[web.1]:
2019-12-06T00:30:47.295669+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2019-12-06T00:30:47.295759+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2019-12-06T00_30_47_289Z-debug.log
2019-12-06T00:30:47.344869+00:00 heroku[web.1]: Process exited with status 1
2019-12-06T00:30:47.369971+00:00 heroku[web.1]: State changed from up to crashed

谢谢你，谢谢你

heroku

8条答案

按热度按时间
kcrjzv8t

kcrjzv8t1#

Contacted heroku support, here I solved the issue:
The error has occurred because the node can only address 1.5GB of memory before hitting the JavaScript heap out of memory error, a default limit that it inherits from the V8 engine. We tweak this default setting on Heroku through the NODE_OPTIONS env var so that the process can address all of the memory available: https://github.com/heroku/heroku-buildpack-nodejs/blob/master/lib/environment.sh#L29-L33
One option would be to specifically call --max_old_space_size=2560 when invoking node to see if that helps alleviate the issue. You can pass that option to Node via environment variable by running the following:

$ heroku config:set NODE_OPTIONS="--max_old_space_size=2560" -a [app_name]

Also adjust the build script to be:

"scripts": {
    "start": "node --max_old_space_size=2560 node_modules/.bin/react-scripts start",
    "build": "node --max_old_space_size=2560 node_modules/.bin/react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  }

Though not really sure build and start scripts change impacting.

赞(0）分享  回复(0）举报  2022-11-13
ylamdve6

ylamdve62#

如果您使用的是免费的dyno版本，请将您的package.jsonstart脚本更改为：

"start": "node --optimize_for_size --max_old_space_size=460 dist/main.js",

更多信息，请访问：https://devcenter.heroku.com/articles/node-memory-use

赞(0）分享  回复(0）举报  2022-11-13
2ledvvac

2ledvvac3#

我唯一能做到这一点的方法是升级到付费的dyno，并将我的package.json中的脚本更改为：

"scripts": {
    "start": "node --max_old_space_size=2048 node_modules/.bin/react-scripts start",
    "build": "node --max_old_space_size=2048 node_modules/.bin/react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  }

不确定是否需要更改脚本。在部署过程中，内存使用量超过1Gb

赞(0）分享  回复(0）举报  2022-11-13
gblwokeq

gblwokeq4#

首先，我对Inovramadani的答案进行了评论，并试图改进该答案，但当我发现其中存在多个问题时，我决定给予自己的答案。在Heroku日志中，我也收到了以下错误：Node doesn 't allow -a flag，因此正确的命令是
heroku config:set NODE_OPTIONS='--max_old_space_size=2560 [app-name]'

赞(0）分享  回复(0）举报  2022-11-13
polkgigr

polkgigr5#

发生这个错误是因为节点在遇到JavaScript heap out of memory错误之前只能寻址1.5GB的内存，这是它从V8引擎继承的默认限制。我们通过NODE_OPTIONS env var在Heroku上调整了这个默认设置，这样进程就可以寻址所有可用的内存。
您可以调整：
1.指定命令（heroku config：set节点选项='--最大旧空间大小=2560 [应用程序名称]'）
1.将新的配置变量添加到“配置变量”部分（在heroku Jmeter 盘-〉设置-〉配置变量中转到您的应用程序）SEE THIS IMAGE!

赞(0）分享  回复(0）举报  2022-11-13
qjp7pelc

qjp7pelc6#

我禁用了Heroku node_modules缓存并正常工作。

heroku config:set NODE_MODULES_CACHE=false
git commit -am 'disable node_modules cache' --allow-empty
git push heroku

您也可以：
1.如果运行时不需要依赖项，则将不必要的依赖项移到devDependencies。
1.使用heroku restart重新启动。

  1. heroku logs --tail以查看日志。
赞(0）分享  回复(0）举报  2022-11-13
gab6jxml

gab6jxml7#

我找到了一个完美的解决方案。
我刚刚降级了一些属性的版本："react-dom"："^16.13.0"和"react-scripts"：package.json文件中的"3.4.0"，并在Heroku中像charm一样工作。
原液来源：https://bismobaruno.medium.com/fixing-memory-heap-reactjs-on-heroku-16910e33e342

赞(0）分享  回复(0）举报  2022-11-13
cedebl8k

cedebl8k8#

You could also try running your React app within a docker container. I'm not confident in why, but this worked for me
This is done by changing your heroku instance to a container by running the following through the heroku cli

heroku stack:set container;

Then adding a dockerfile

#dockerfile
# syntax=docker/dockerfile:1
FROM node:latest
WORKDIR /app

COPY ["package.json", "package-lock.json*", "./"]
RUN npm install
COPY . .
RUN npm run build
EXPOSE 3000
#Either run in normally
CMD ["npm","start"]

#or run in production
#RUN npm install -g serve
#CMD [ "serve", "-s", "build" ]

and a heroku.yml

#heroku.yml
build:
  docker:
    web: dockerfile
赞(0）分享  回复(0）举报  2022-11-13
我来回答

相关问题

    查看更多

    热门标签

    更多
    JavaquerypythonNode开发语言requestUtil数据库Table后端算法LoggerMessageElementParser

    最新问答

    更多
    • 蜀ICP备2022004421号-2 NULL123 https://www.null123.com © All rights reserved
    • 本站内容来源互联网,如果侵犯您的权益请联系我们删除, 联系方式：448109455@qq.com