javascript heap out of memory webpack javascript heap out of memory webpack

Nothing helps. It will be good if anyone could solve this problem. Short story taking place on a toroidal planet or moon involving flying, How do you get out of a corner when plotting yourself into a corner. Still didnt work. Ran into the same situation in our project where we are using serverless-webpack to individually package 28 lambdas with typescript. cache.idleTimeoutAfterLargeChanges option is only available when cache.type is set to 'filesystem'. 9: 00007FF7B1745EB7 v8::internal::Heap::RootIsImmortalImmovable+5703 javascript heap out of memory webpack - The AI Search Engine You Ability to ignore files/directories for rebuilds/compiles. Issue @andrewrothman The workaround that worked for my project is by turning off package.individually: true. All I can say is this: the different between my npm start and build script is that the build runs. The difference between the phonemes /p/ and /b/ in Japanese. Staging Ground Beta 1 Recap, and Reviewers needed for Beta 2. If aws-sdk should be packaged, you can either put it into your devDependencies or use. Is there any solution available ? The build process just runs a command to build a react app using webpack. To fix JavaScript heap out of memory error, you need to add the --max-old-space-size option when running your npm command. - subnet-0c92a13e1d6b93630 V 1.1.1 includes a fix for a regression when working with some other plugins: https://github.com/Realytics/fork-ts-checker-webpack-plugin/releases/tag/v1.1.1 and this may resolve your issue. The one liner below has worked for some. Fatal error call and retry last allocation failed process out of memory Apart from that, he is also a sports enthusiast. EDIT: Also make sure you read https://github.com/webpack/webpack/issues/6389 if you are thinking of downgrading to webpack 4. was back on webpack 1), so I don't think the solution here should be @daniel-cottone please share your thoughts after u succeed. @daniel-cottone I've been dealing with the same issue for a couple weeks now. minimize: false What I've found there is const division = parseInt(process.env.WORK_DIVISION, 10); which seems to control the amount of worker processes spawned for the plugin. Regardless of your IDE, the "JavaScript heap out of memory" fix is identical. This ran fine for weeks at a time without restarted the dev server on webpack 3. Hi @daniel-cottone , Site design / logo 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA. }, @grumpy-programmer Webpack out of memory - Stack Overflow Does Counterspell prevent from any further spells being cast on a given turn? In my case it was only used by the mini-css-extract-plugin coming from create-react-app's defaults. prod: live What are you using instead of webpack-dev-server? on my project, when i save any file, webpack-dev-server/webpack consumes 5% more of my memory, even if i din`t change anything at all on the file, and the memory consumption keeps incensing on steps of 5% of my total ram, to the point where it freezes my computer and now i have to use a system manager on daily basis to work, and kill the process when i only have 10% of ram left. I tried the solution suggested above of using webpack-dev-server but it hangs(?) Thanks for contributing an answer to Stack Overflow! fwiw I implemented the changes that @dashmug mentioned in his post and it looks like my current project is back in business. local: ${ssm:/database/dev/user} I had remove package individually and it works, but I want to use that feature again. staging: ${ssm:/database/prod/host} To learn more, see our tips on writing great answers. The memory size starts from 1024 for 1GB: Alternatively, you can also set the memory limit for your entire environment using a configuration file. This can be something with your configuration. wrote: I don't even understand why this is an issue here. 2021-01-06: not yet calculated FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memoryinfo - Cre. Reply to this email directly, view it on GitHub Try using Gatsby Cloud. The longer build outweighs the better startup behavior (if the lambdas are cold started) and if some big dependencies are only used by one function. - subnet-0c92a13e1d6b93630 }, 11: 00007FF7B187DC6D v8::internal::Factory::AllocateRawArray+61 This is further confirmed when tested with thread-loader, the timer increases individually in each thread. I just encountered the same error with my webpack configuration and I was able to resolve it by updating my dependencies. Call it a day. Screenshot from node-gc-viewer below. securityGroupIds: Yes that. Thanks for the Memory(s) Part I - Medium However, there are some issues in the webpack repository about the OOM issues in combination of source maps. I can try, I am getting this error while working on a child compiler thing, so that is why I think this is a hot candidate. @j0k3r I can confirm that the concurrency setting added in #681 works as intended after update to 5.4.0 (i.e. cache.store tells webpack when to store data on the file system. V8 Ineffective mark-compacts near heap limit Allocation failed - Javascript heap out of memory --max_old_space_size= {MB} Node.js npm scripts Webpcak 4: 0x1001f68c7 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/konnorrogers/.asdf/installs/nodejs/14.17.2/bin/node] If yes would it be okay for you if we'd provide a PR? @mikemaccana This issue is over almost 3 years old, I can't remember the specifics, but the line above automagically fixed it for me after wasting hours on finding the exact issue. Hmmm that sounds like a memory leak somewhere when using individual packaging. exclude: [path.resolve(__dirname, 'node_modules')]. - subnet-0c92a13e1d6b93630 Staging Ground Beta 1 Recap, and Reviewers needed for Beta 2, How to set Linux environment variables with Ansible, Heap out of memory - increasing max-old-space-size didn't solve the issue, NPM script Webpack --json : JavaScript heap out of memory, Build Angular App on Rasperry Pi causes Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory, Error: Cannot find module 'webpack-cli/bin/config-yargs', Webpack Error - configuration.node has an unknown property 'fs', npm not start. }, JavaScript heap out of memory "node --max-old-space-size=10240"' package.individually not set helps with this problem. I'm using a combination of fork-ts-checker-webpack-plugin, cache-loader and thread-loader to compile 11 typescript lambda functions but I'm getting this error; I'm now stuck because I can no longer deploy any of my functions. 5: 00007FF7B1694487 v8::internal::FatalProcessOutOfMemory+599 This guarantees that memory is cleaned up after every compile, since we kill the process, and can compile multiple functions at once. method: get Did it also happen for you with a serverless package? You can add an environment variable through Control Panel to increase the memory allocated to a Node.js project. We've reverted back to not packaging individually because of excessive memory consumption from webpack's multiple compiler. Please use latest terser-webpack-plugin version, Facing this issue in may 2020, solved it updating node to 12.16.3 thanks to https://stackoverflow.com/questions/53230823/fatal-error-ineffective-mark-compacts-near-heap-limit-allocation-failed-javas, I've had luck reducing the memory usage quite a bit by replacing any call to [contenthash] with [chunkhash]. 4: 00007FF6C67626FE v8::internal::FatalProcessOutOfMemory+846 Adding --compile-concurrency 3 fixed problem for me, @j0k3r I'm on 5.5.1 and still have this issue unfortunately. Locations for the cache. If increasing the memory . I ran into this problem as well, here's my experience with several of the alternatives discussed in this thread: Hope this is useful to someone and they don't have to spend a whole day on it like I did :smile: Can someone confirme this has been improved or fixed by 5.4.0? Over ten years of software development experience from scripting language to object-oriented programming (TCL/C/C++/C#/Javascript/Java/Python/React/NodeJS), Microsoft.NET technologies,. - http: Operating System: Ubuntu 18.04 This is vague - what version of postcss-loader has the memory leak? In this article we are going to discuss about JavaScript heap out memory issue which used to happen in Angular project. ], Hi, Im having this same issue. My first question: what does the number 1829 (and 2279) represents exactly ? cache.idleTimeoutForInitialStore option is only available when cache.type is set to 'filesystem'. Maybe a solution would be to provide a PR for the ts-checker plugin that limits the number of spawned processes when using multi-compiles in webpack. So I think you guys are looking in the wrong place by saying this leak is a leak in webpacks watch code. MAPBOX_KEY: pk.eyJ1IjoibWFydGlubG9ja2V0dCIsImEiOiJjam80bDJ1aTgwMTNjM3dvNm9vcTlndml4In0.F2oPsuIGwgI26XsS8PRWjA, custom: An update: it works when I set transpileOnly: true for ts-loader. I think child compiler + watch mode = fatal heap memory error. With the dev server running, with each change my rebuild time gets about a second longer than the previous one, before crashing at about 50 seconds. In the issue at the next repo the problem was cause by chakra ui which also uses emotion under the hood, Facing this issue on a custom setup (no next/cra, custom webpack and dev server configs) using mui which uses emotion under the hood. Now the application is back to its previous size and the build does not indur a heap overflow. 13: 0x100a81a79 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/Users/konnorrogers/.asdf/installs/nodejs/14.17.2/bin/node] This fix will only improve memory usage when packaging many functions, anything under ~8 functions probably won't make a difference since they will be packaged concurrently. @grumpy-programmer It's a workaround that worked on my local but didn't work on our CI environment (AWS CodeBuild using 3GB). cache.maxMemoryGenerations: defaults to 10 in development mode and to Infinity in production mode. I'm also getting this issue recently after my project started to increase in size. I am struggling with this issue. Compression type used for the cache files. Mutually exclusive execution using std::atomic? Fixing FATAL ERROR: Ineffective mark-compacts near heap limit We finally hit the same error - Javascript heap out of memory - that's already been reported. your inbox! 9: 0x10039f2e0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/konnorrogers/.asdf/installs/nodejs/14.17.2/bin/node] const slsw = require('serverless-webpack'); To disable caching pass false: While setting cache.type to 'filesystem' opens up more options for configuration. "build": "export NODE_OPTIONS=--max_old_space_size=8192 && webpack --config webpack.prod.js". Lc theo: Ngn sch. Doubling the cube, field extensions and minimal polynoms. - sg-0a328af91b6508ffd plugins: [ Previously, we were on webpack 3.12.0 and webpack-dev-server 2.11.3, and now we're on webpack 4.22.0 and webpack-dev-server 3.1.10. Cache | webpack @shanmugarajbe please provide minimum reproducible test repo and create new issue. 7: 00007FF7B173DD72 v8::internal::Heap::CollectGarbage+7234 handler: functions/rest/routesHandler.mainApi Gotcha, can confirm it persists after updating as well. If this is not the issue, you can increase the node.js memory (it defaults to 1.7 GB, which can be too few for big builds). When I deploy the service I got a JavaScript heap out of memory. Is it suspicious or odd to stand by the gate of a GA airport watching the planes? The first try should be to disable some plugins in the webpack.config and check if the ts-loader might allocate all the memory. No dice. add an environment variable through Control Panel. Nothing. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. MYSQL_USER: ${self:custom.mysqlUser.${self:provider.stage}} Most of the entries in the NAME column of the output from lsof +D /tmp do not begin with /tmp. - JavaScript heap out of memory Node.js . 3: 00007FF6C6448910 node_module_register+2032 Much appreciated effort, Grumpy! I have 7 functions, but Making statements based on opinion; back them up with references or personal experience. subnetIds: I have tried running the command in the same docker container locally and it works without any issues whatsoever so I am led to thinking the issue likely comes from the Gitlab runner. The one liner below has worked for some. The reason why the application got suddenly bigger is an import. target: 'node', If you don't have any other option, maybe you can try this out. CI should have an option to share cache between builds. method: post }; AWS Lambda - Nodejs: Allocation failed - JavaScript heap out of memory, FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory error, webpack-node-externals - JavaScript heap out of memory, Angular 5.2 : Getting error while building application using VSTS build server : CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory, How to fix "FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory" error, How to Polyfill node core modules in webpack 5. cache.buildDependencies is an object of arrays of additional code dependencies for the build. ); module.exports = { By default it is false for development mode and 'gzip' for production mode. new webpack.DefinePlugin({ "global.GENTLY": false }) Run this instead of "webpack". subnetIds: It works but I don't think it's necessary. I very much appreciate the hard work that has gone into this open source project and thank all the contributors/maintainers, but this seems like a serious issue for using this plugin in production. To learn more, see our tips on writing great answers. vpc: With multi-compile mode you mean that serverless-webpack "multiplies" the webpack config for each function - like so: https://webpack.js.org/configuration/configuration-types/#exporting-multiple-configurations, I could not find anything else that sounds like multi-compile mode. Hi everyone, - sg-0a328af91b6508ffd I've been trying many of the answers in this thread, with no luck. See Node.js crypto for more details. 'development' : 'production', path: graphql And I know that there are issues with the This issue generally will happen if your project is really big or wrongly designed. I have the same issue in a monorepo with 10+ services. [17208:0000020B4EB70F20] 1185036 ms: Scavenge 3367.7 (4163.5) -> 3366.9 (4164.0) MB, 9.7 / 0.0 ms (average mu = 0.164, current mu = 0.189) allocation failure, ==== JS stack trace =========================================. events: staging: 3306 Do roots of these polynomials approach the negative of the Euler-Mascheroni constant? prod: ${ssm:/database/prod/user} We have next js project that persists cache on the disk and the pak files are close to 200MB. events: However, version 2.x did not support individual packaging (in fact it only copied the whole artifact per function). path: /api/util/api-key-generator Gregveres, could you please share your solution? To setup cache: // This makes all dependencies of this file - build dependencies, // By default webpack and loaders are build dependencies, # fallback to use "main" branch cache, requires GitLab Runner 13.4, # make sure that you don't run "npm ci" in this job or change default cache directory, # otherwise "npm ci" will prune cache files. Have a question about this project? - subnet-0a5e882de1e95480b My build is not passing through CI and I do not want to go back to https://github.com/prisma/serverless-plugin-typescript because it is using an outdated version of typescript and appears to be looking for maintainers. Connect and share knowledge within a single location that is structured and easy to search. Reducing crashes in generating Javascript bundles & serializing HTML pages. When they are used again they will be deserialized from the disk. Time in milliseconds. events: The issue is caused by a memory leak in postcss-loader. 4: 00007FF7B169454E v8::internal::FatalProcessOutOfMemory+798 privacy statement. better optimization-wise, but webpack itself is invoked only once and does Note that in my case I run it with a value of 3 in the CI build; I have it configured in serverless.yml as follows: In CI, I deploy as follows: cache.maxGenerations: 1: Cache entries are removed after being unused for a single compilation. handler: functions/graphql/handler.graphqlHandler Call it a day. I tried a lot of things to fix it but the only thing that worked was setting: I'm at a loss as to why this works, but I suspect it may have something to do with creating more small common chunks that do not change between recompiles? Webpack javascript Heap out of memory - large number of modules Vuejs with Laravel production: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Ask Question Asked yesterday In there are emotion strings that have a line length of > 22000 (22k) characters. cache.name option is only available when cache.type is set to 'filesystem'. How to solve JavaScript heap out of memory error method: get @dashmug I tried the RC two days ago and it didnt fix the problem for me. I am running a pipeline which has a build stage as part of it which is failing due to running out of memory. focused on changing the loaders configurations, but on the way that Has anyone encountered a similar problem? I have the same problem but without TS. node --max-old-space-size=8192 node_modules/webpack-dev-server/bin/webpack-dev-server.js, @B3zo0 I don`t think increase the max-old-space-size is a good solution, even though I have not better solution. You'll find the zip packages that would be uploaded in the .serverless directory. timeout: 30 thanks for reporting. I was wrong about the caching plugin helping out. Asking for help, clarification, or responding to other answers. Remove the cache. The amount of time in milliseconds that unused cache entries are allowed to stay in the filesystem cache; defaults to one month. I tried a number of other node specific fixes. The overall size of the project is a very small project, I run projects much bigger with webpack with the same loaders (and more stuff) and almost never fall on this heap errors (the last I remember was back on webpack 1), so I don't think the solution here should be focused on changing the loaders configurations, but on the way that serverless-webpack is executing webpack. You might get away with the following. 2: 00007FF6C6447F96 node::MakeCallback+4534 Applying #570 would solve our problem but would break. I've made your suggested changes to webpack externals and have added the webpackIncludeModules configuration to serverless custom config; I still seem to be experiencing the same problem though. @akleiber Is this a quite big project where it happens? Webpack - Qiita ASP.NET is better suited for large and medium-sized organizations, whereas PHP is better equipped to serve start-ups and small-sized organizations. It also persisted in this state through multiple machine resets and I wrangled with this for over an hour. handler: functions/rest/routesHandler.alexa_search_stations It completed OK. Do I need to be concerned about the +645 hidden modules? Then it's more clear how to reproduce it and we can find a solution. However I do not know, if the webpack library will free the allocated resources after the compile again. My code is GPL licensed, can I issue a license to have my code be distributed in a specific MIT licensed project? Thanks! When I try to upgrade to a later version of serverless-webpack and run sls webpack, the build will run for about a minute and then I get the following error: If I change my serverless config to not package individually, package: individually: false then this error goes away. This is seeming more and more like a core webpack issue. wds: webpack output is served from /packs/ rev2023.3.3.43278. I had to give up on webpack-dev-server because it crashed on the first code change every single time. MYSQL_PORT: ${self:custom.mysqlPort.${self:provider.stage}} JavaScript heap out of memory nodejs V8641.4g4gworker So in the worst case memory usage is lambda count * memory limit. So for finding the root issue, we should concentrate on the webpack step and especially typescript. 3: 0x1000b23ef node::OnFatalError(char const*, char const*) [/Users/konnorrogers/.asdf/installs/nodejs/14.17.2/bin/node] We are not affiliated with GitHub, Inc. or with any developers who use GitHub for their projects. 2: 0x1000b2289 node::Abort() [/Users/konnorrogers/.asdf/installs/nodejs/14.17.2/bin/node] handler: functions/rest/routesHandler.alexa_qualify_location This is still happening all the time for me. Check the memoryLimit option in the ForkTsCheckerWebpackPlugin configuration. This behavior matches the log above: It crashed for you at the webpack step! Proper memory management is crucial when writing your programs, especially in a low-level language. In your terminal, before you run your project, enter the following command and press Enter: This will allocate 4GB of virtual memory to the execution space of Node.js. test: /\.(woff(2)?|ttf|eot|otf)(\?v=\d+\.\d+\.\d+)?$/. FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory, FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory. . Why does Mister Mxyzptlk need to have a weakness in the comics? your node_modules/.bin/* files. Replacing broken pins/legs on a DIP IC package, Bulk update symbol size units from mm to map units in rule-based symbology. I think changing the title to "JavaScript heap out of memory when _packaging_ many functions" makes more sense now that it has been isolated to just the packaging process and not the deployment process. The application is initially quiet big and due to a necessary modification, it got bigger and now I'm getting this error: First of all, I noticed an increase of a number in webpack output when I run a simple build without uglifying and minifying, which i'm guessing is the number of modules compiled by webpack: As you can see, we went from 1829 (+1815 hidden modules) to 2279 (+2265 hidden modules). all of them are very small. Hey @HyperBrain thanks for quick response. - prod externals: ['aws-sdk', 'utf-8-validate', 'bufferutil'], Reinstalling every module because you have a problem with one isn't a good fix. `, provider: it that why its taking so long perhaps? apiGateway: true The caching plugin is in my common file for my webpack config. if(typeof ez_ad_units != 'undefined'){ez_ad_units.push([[580,400],'sebhastian_com-large-leaderboard-2','ezslot_3',133,'0','0'])};__ez_fad_position('div-gpt-ad-sebhastian_com-large-leaderboard-2-0');To fix JavaScript heap out of memory error, you need to add the --max-old-space-size option when running your npm command. it seems that increasing the memory as suggested only make the issue less likely to happen rather than eliminating the issue. Time in milliseconds. I am fairly confident that the problem is at least minimized to unnoticeable even for 200+ lambdas. There's a memory issue in webpack-dev-server and/or webpack 4. 15: 00007FF7B194F6B4 v8::internal::StoreBuffer::StoreBufferOverflow+123924 An attacker can entice the victim to open a document to trigger this vulnerability. The install stage is the one that fails with the following message (also see attached): FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory. key => (entries[key] = ['./source-map-install.js', slsw.lib.entries[key]]) FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory How to use When I'm working with a webpack-dev server, the problem sometimes occurs. This is in addition to { splitChunks: { chunks: 'all' } }, Ie: JavaScript heap out of memory with simple webpack build - GitLab Can airtags be tracked from an iMac desktop, with no iPhone? In this paper, we propose a framework, called JS Capsules, for characterizing the memory of JavaScript functions and, using this framework, we investigate the key browser mechanics that contribute to the memory overhead. Yes that. node --max-old-space-size=4096 node_modules/serverless/bin/serverless package to 4GB and check if it then passes with the full amount of functions. I have a serverless project with a lot of functions 75+. Start node with command-line flag --max-old-space-size=2048 (to 2GB, default is 512 MB I think), or set it via environment variable NODE_OPTS https://nodejs.org/api/cli.html. serverless-webpack - JavaScript heap out of memory when packaging The number of functions we managed to compile depended on the memory allocated to the process, so eventually this would lead to the same problem of having to continually increase the memory forever. So what was the fix then? limits the number of concurrent compiles in the CI system thus effectively limiting the amount of necessary memory and avoiding the out-of-memory errors). Bought a new laptop with I8 quad core and 16 gb of ram and this issue is happening more often than on my I5 duo with 8 gb of ram?? [contenthash:8].css' -> 'static/css/[name].[chunkhash:8].css'. Can you point me to the right line - I guess something here is responsible https://github.com/serverless-heaven/serverless-webpack/blob/master/lib/packageModules.js. }, // Workaround for ws module trying to require devDependencies cache.idleTimeout option is only available when cache.type is set to 'filesystem'. changeable? Here you can see my webpack config for the production build, nothing out of the ordinary: Here is the build command in the package.json along with the node version set in the engine that matches the docker images node version, I have tried setting the max_old_space_size node option as I have found recommended online but it does not change anything no matter what memory value I give it, image: cypress/browsers:node14.7.0-chrome84, CYPRESS_CACHE_FOLDER: '$CI_PROJECT_DIR/cache/Cypress'. To set a different amount of memory, replace 4096 with the required amount in MB. Here is the pipeline config gitlab-ci: I am using a cypress docker image (cypress/browsers:node14.7.0-chrome84) to run the pipeline. region: eu-west-2 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. securityGroupIds: vpc: Can I tell police to wait and call a lawyer when served with a search warrant? Upgrading webpack from 5.11 to 5.37.1 slows down the increments, but, still, it is surely increasing gradually from 70s to 700s+ at the 50th entry. Only gripe I could have is that the type checking doesn't fail fast; if you would prefer to check types before you even start the build, which could take some time, then maybe tsc --noEmit is a better option. I have not seen improvements with 5.4.0. webpackJavaScript heap out of memory - It doesnt. Memory errors can be scary and confusing, but this Node.js one is easy to fix. JavaScript Heap Out of Memory: How to Free Memory Seamlessly 1: 00007FF7B12BD7AA v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4618 This seems to be a Serverless Framework problem. 11 comments dantman commented on Jun 10, 2022 In the same project under CRAv4 and Storybook (same version) with Webpack 4, Storybook successfully builds at the default memory limit Seraph Trn - Senior Software Engineer - VALD | LinkedIn I have 73 entry points and a few hundred TS files. 5: 0x1001f6863 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/konnorrogers/.asdf/installs/nodejs/14.17.2/bin/node] LaravelVue.js _ I have 8GB of RAM. Why are physically impossible and logically impossible concepts considered separate in terms of probability? mode: "production", 8: 0x1003a19b5 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/konnorrogers/.asdf/installs/nodejs/14.17.2/bin/node] extra info: I too facing the same issue with the latest webpack. vuejavascript heap out of memory_-CSDN