René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"extractLicense: true leads to huge memory utilization (Out of memory)","articleBody":"\u003c!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅\r\n\r\nOh hi there! 😄\r\n\r\nTo expedite issue processing please search open and closed issues before submitting a new one.\r\nExisting issues often contain information about workarounds, resolution, or progress updates.\r\n\r\n🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅--\u003e\r\n\r\n\r\n# 🐞 Bug report\r\n\r\n### Command (mark with an `x`)\r\n\u003c!-- Can you pin-point the command or commands that are effected by this bug? --\u003e\r\n\u003c!-- ✍️edit: --\u003e\r\n\r\n- [ ] new\r\n- [x] build\r\n- [ ] serve\r\n- [ ] test\r\n- [ ] e2e\r\n- [ ] generate\r\n- [ ] add\r\n- [ ] update\r\n- [ ] lint\r\n- [ ] xi18n\r\n- [ ] run\r\n- [ ] config\r\n- [ ] help\r\n- [ ] version\r\n- [ ] doc\r\n\r\n\r\n### Is this a regression?\r\n\r\n\u003c!-- Did this behavior use to work in the previous version? --\u003e\r\nNo\r\n\r\n\r\n### Description\r\n\r\n\u003c!-- ✍️--\u003e A clear and concise description of the problem...\r\nRecently we started to see a huge jump of memory utilization and our CI failing while building our project. it was under 4GB whenever we were building our project. but the recent scenario was exhausting all the memory that is available. My system has 16GB of RAM and it is exhausting all of it. upon further inspection I found that we have a few extra License.txt files for a few modules. so I tried experimenting with `extractLicense: false`, so the License.txt files of those modules still remains but there was no 3rdpartylicense.txt file but the memory leak was fixed. I suspect there is a memory leak while trying to extract the licenses.\r\n\r\n## 🔬 Minimal Reproduction\r\n\u003c!--\r\nSimple steps to reproduce this bug.\r\n\r\nPlease include: commands run (including args), packages added, related code changes.\r\n\r\nIf reproduction steps are not enough for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue. \r\nA good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem. \r\nShare the link to the repo below along with step-by-step instructions to reproduce the problem, as well as expected and actual behavior.\r\n\r\nIssues that don't have enough info and can't be reproduced will be closed.\r\n\r\nYou can read more about issue submission guidelines here: https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-submitting-an-issue\r\n--\u003e\r\nNot available. The only thing I know is how to fix it is by turning off the license extraction \r\n`extractLicense: false`\r\n## 🔥 Exception or Error\r\n\u003cpre\u003eng build --prod\r\n92% chunk asset optimization TerserPlugin\r\n\u003c--- Last few GCs ---\u003e\r\n\r\n[10441:0x27758c0]   148425 ms: Mark-sweep 1290.5 (1454.7) -\u003e 1258.8 (1432.9) MB, 837.0 / 0.0 ms  (average mu = 0.135, current mu = 0.071) allocation failure GC in old space requested\r\n[10441:0x27758c0]   149000 ms: Mark-sweep 1283.7 (1442.0) -\u003e 1269.6 (1428.4) MB, 461.8 / 0.0 ms  (average mu = 0.160, current mu = 0.196) allocation failure scavenge might not succeed\r\n\r\n\r\n\u003c--- JS stacktrace ---\u003e\r\n\r\n==== JS stack trace =========================================\r\n\r\n    0: ExitFrame [pc: 0xe7dd74dbe1d]\r\n    1: StubFrame [pc: 0xe7dd74cb681]\r\nSecurity context: 0x0e76c7b9e6c1 \u003cJSObject\u003e\r\n    2: replace [0xe76c7b905c1](this=0x179f3f5823c9 \u003cVery long string[6525248]\u003e,0x0a5861ec80c9 \u003cJSRegExp \u003cString[18]: [\u003c\u003e\\/\\u2028\\u2029]\u003e\u003e,0x0a5861ec8161 \u003cJSFunction escapeUnsafeChars (sfi = 0x2520c85dce9)\u003e)\r\n    3: serialize(aka serialize) [0x2520c85e401] [/home/neurosensum/Neurosensum repository/portal/node_modules/seriali...\r\n\r\nFATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory\r\n 1: 0x8fb090 node::Abort() [ng build --prod]\r\n 2: 0x8fb0dc  [ng build --prod]\r\n 3: 0xb0322e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [ng build --prod]\r\n 4: 0xb03464 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [ng build --prod]\r\n 5: 0xef74c2  [ng build --prod]\r\n 6: 0xef75c8 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [ng build --prod]\r\n 7: 0xf036a2 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [ng build --prod]\r\n 8: 0xf03fd4 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [ng build --prod]\r\n 9: 0xf06c41 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [ng build --prod]\r\n10: 0xed688b v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [ng build --prod]\r\n11: 0x11c5371 v8::internal::Runtime_StringBuilderConcat(int, v8::internal::Object**, v8::internal::Isolate*) [ng build --prod]\r\n12: 0xe7dd74dbe1d \r\nAborted (core dumped)\u003c/pre\u003e\r\n\r\n\r\n## 🌍 Your Environment\r\n\u003cpre\u003e\r\n     _                      _                 ____ _     ___\r\n    / \\   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|\r\n   / △ \\ | '_ \\ / _` | | | | |/ _` | '__|   | |   | |    | |\r\n  / ___ \\| | | | (_| | |_| | | (_| | |      | |___| |___ | |\r\n /_/   \\_\\_| |_|\\__, |\\__,_|_|\\__,_|_|       \\____|_____|___|\r\n                |___/\r\n    \r\n\r\nAngular CLI: 8.1.3\r\nNode: 12.16.3\r\nOS: win32 x64\r\nAngular: 8.1.3\r\n... cli, common, compiler, compiler-cli, core, forms\r\n... language-service, platform-browser, platform-browser-dynamic\r\n... router\r\n\r\nPackage                            Version\r\n------------------------------------------------------------\r\n@angular-devkit/architect          0.803.28\r\n@angular-devkit/build-angular      0.803.28\r\n@angular-devkit/build-ng-packagr   0.801.3\r\n@angular-devkit/build-optimizer    0.803.28\r\n@angular-devkit/build-webpack      0.803.28\r\n@angular-devkit/core               8.3.28\r\n@angular-devkit/schematics         8.1.3\r\n@angular/animations                8.2.14\r\n@angular/cdk                       8.2.3\r\n@angular/material                  8.2.3\r\n@ngtools/webpack                   8.3.28\r\n@schematics/angular                8.1.3\r\n@schematics/update                 0.801.3\r\nng-packagr                         5.7.1\r\nrxjs                               6.4.0\r\ntypescript                         3.4.5\r\nwebpack                            4.39.2\u003c/pre\u003e\r\n\r\n**Anything else relevant?**\r\n\u003c!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. --\u003e\r\n\r\n\u003c!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. --\u003e\r\n\r\nWe had this issue earlier also but we thought this is something related to our code so we reverted the one commit where it all started and somehow managed to get the build working. Also the build gives a Out of memory exception on Linux where as in windows it exhausts all the memory but ensures that the build happens, despite having the same amount of RAM.","author":{"url":"https://github.com/cray2015","@type":"Person","name":"cray2015"},"datePublished":"2020-06-30T07:25:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/18076/angular-cli/issues/18076"}