Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

can no longer run yarn dev #151

Closed
GlenDC opened this issue Jun 26, 2019 · 4 comments
Closed

can no longer run yarn dev #151

GlenDC opened this issue Jun 26, 2019 · 4 comments
Assignees
Labels
priority_critical type_bug Something isn't working

Comments

@GlenDC
Copy link
Contributor

GlenDC commented Jun 26, 2019

yarn dev
yarn run v1.10.1
$ cross-env START_HOT=1 node --max-old-space-size=8192 -r @babel/register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 yarn start-renderer-dev
$ cross-env NODE_ENV=development webpack-dev-server --config configs/webpack.config.renderer.dev.babel.js
Starting Main Process...
npm WARN lifecycle The node binary used for scripts is /var/folders/8v/hhd27nsd2kq2xtvjyv68l1lr0000gn/T/yarn--1561536820642-0.9501342016064589/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

> tfchain-wallet@0.1.3 start-main-dev /Users/glendc/oss/github.com/threefoldfoundation/tfchain-wallet-electron
> cross-env HOT=1 NODE_ENV=development electron -r @babel/register ./app/main.dev.js

2019-06-26 10:13:46.330 Electron[1256:9848] *** WARNING: Textured window <EventDispatchingWindow: 0x7fa5ded37460> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.

<--- Last few GCs --->

[1238:0x102483000]    22001 ms: Scavenge 1371.5 (1424.7) -> 1370.5 (1424.7) MB, 2.0 / 0.0 ms  (average mu = 0.177, current mu = 0.119) allocation failure 
[1238:0x102483000]    22004 ms: Scavenge 1371.5 (1424.7) -> 1370.5 (1424.7) MB, 2.0 / 0.0 ms  (average mu = 0.177, current mu = 0.119) allocation failure 
[1238:0x102483000]    22008 ms: Scavenge 1371.5 (1424.7) -> 1370.5 (1425.2) MB, 2.1 / 0.0 ms  (average mu = 0.177, current mu = 0.119) allocation failure 


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 0x3648720041bd]
Security context: 0x2dfca221e6c9 <JSObject>
    1: eachOverlappingGeneratedOutputRange(aka eachOverlappingGeneratedOutputRange) [0x2dfc97dc4e39] [/Users/glendc/oss/github.com/threefoldfoundation/tfchain-wallet-electron/node_modules/@babel/core/lib/transformation/file/merge-map.js:~95] [pc=0x364872b8dc94](this=0x2dfcad5822e1 <undefined>,outputFile=0x2dfcef27b311 <Object map = 0x2dfcbabc3129>,inputGener...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x100033c31 node::Abort() [/usr/local/bin/node]
 2: 0x1000353ea node::FatalTryCatch::~FatalTryCatch() [/usr/local/bin/node]
 3: 0x10019bc9a v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 4: 0x10056a072 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
 5: 0x100569029 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
 6: 0x100566cb8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
 7: 0x1005731fc v8::internal::Heap::AllocateRawWithRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
 8: 0x100541b94 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/usr/local/bin/node]
 9: 0x1007cb394 v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
10: 0x3648720041bd 
11: 0x364872b8dc94 
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [dev] Error 1

I already tried to restart my computer. I have 12+ GB free in RAM, so should be OK.

@GlenDC GlenDC added type_bug Something isn't working priority_critical labels Jun 26, 2019
@GlenDC GlenDC added this to To do in v0.2.0 (Alpha 2.0) via automation Jun 26, 2019
@GlenDC GlenDC self-assigned this Jun 26, 2019
@GlenDC
Copy link
Contributor Author

GlenDC commented Jun 26, 2019

Checked many related open issues in other projects, also stackoverflow. Nothing seems to help...

@GlenDC
Copy link
Contributor Author

GlenDC commented Jun 26, 2019

Tried deleting the node_modules folder, and re-run npm install. Still same error when doing yarn dev...

@GlenDC
Copy link
Contributor Author

GlenDC commented Jun 26, 2019

https://www.npmjs.com/package/increase-memory-limit also doesn't seem to be any good, pretty dumb tool that replaces way too much in the node_modules bin dir...

@GlenDC GlenDC closed this as completed in adc5c1c Jun 26, 2019
v0.2.0 (Alpha 2.0) automation moved this from To do to Done Jun 26, 2019
@GlenDC
Copy link
Contributor Author

GlenDC commented Jun 26, 2019

webpack/webpack#1914 (comment) was the comment that finally made it work again for me...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority_critical type_bug Something isn't working
Projects
No open projects
Development

No branches or pull requests

2 participants