Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 3.3.0: JavaScript heap out of memory (worked fine in 3.2.0) #8110

Closed
lamqson opened this issue Dec 6, 2019 · 2 comments
Closed

Version 3.3.0: JavaScript heap out of memory (worked fine in 3.2.0) #8110

lamqson opened this issue Dec 6, 2019 · 2 comments

Comments

@lamqson
Copy link

lamqson commented Dec 6, 2019

Describe the bug

After upgrading to version 3.3.0

<--- Last few GCs --->

[33636:0x1040b7000] 79517 ms: Scavenge 2029.6 (2050.5) -> 2029.0 (2050.5) MB, 4.4 / 0.0 ms (average mu = 0.153, current mu = 0.000) allocation failure
[33636:0x1040b7000] 79522 ms: Scavenge 2029.7 (2050.5) -> 2029.4 (2050.8) MB, 4.7 / 0.0 ms (average mu = 0.153, current mu = 0.000) allocation failure
[33636:0x1040b7000] 79529 ms: Scavenge 2029.9 (2050.8) -> 2029.5 (2051.5) MB, 5.5 / 0.0 ms (average mu = 0.153, current mu = 0.000) allocation failure

<--- JS stacktrace --->

==== JS stack trace =========================================

0: ExitFrame [pc: 0x100951859]

Security context: 0x300891480921
1: SourceMapConsumer_allGeneratedPositionsFor [0x30082537e701] [/Users/sonlam/workspaces/octupi/raindrop/node_modules/react-scripts/node_modules/source-map/lib/source-map-consumer.js:~178] [pc=0x2f45946614a4](this=0x30082c3a7201 ,0x3008b7c1b8c1 )
2: /* anonymous /(aka / anonymou...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Writing Node.js report to file: report.20191206.113108.33636.0.001.json
Node.js report completed
1: 0x100081683 node::Abort() [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
2: 0x100081807 node::OnFatalError(char const*, char const*) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
3: 0x10017fd37 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
4: 0x10017fcd3 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
5: 0x1003083b5 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
6: 0x100309a84 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
7: 0x100306850 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
8: 0x100304866 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
9: 0x1003103ea v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
10: 0x100310471 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
11: 0x1002dd1c6 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
12: 0x10061e778 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
13: 0x100951859 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/Users/sonlam/.nvm/versions/node/v13.3.0/bin/node]
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Did you try recovering your dependencies?

(Write your answer here.)

Which terms did you search for in User Guide?

(Write your answer here if relevant.)

Environment

(paste the output of the command here.)

Steps to reproduce

(Write your steps here:)

Expected behavior

(Write what you thought would happen.)

Actual behavior

(Write what happened. Please add screenshots!)

Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

@lamqson lamqson changed the title Version 3.3.0: JavaScript heap out of memory, worked fine in 3.2.0 Version 3.3.0: JavaScript heap out of memory (worked fine in 3.2.0) Dec 6, 2019
@daviseford
Copy link

Related to #8096

@heyimalex
Copy link
Contributor

Duplicate of #8096

@heyimalex heyimalex marked this as a duplicate of #8096 Dec 6, 2019
@lock lock bot locked and limited conversation to collaborators Dec 11, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants