search

reactioncommerce / reaction-cli

A command line tool for working with Reaction Commerce.
33 stars 20 forks source link

meteor 1.5 and reaction-cli not going well together-- windows 10 #34

Closed hrath2015 closed 6 years ago

hrath2015 commented 7 years ago

Keep getting the error on reactionrun 

=> Started proxy.
=> Started MongoDB.
cfs:gridfs: updating npm dependencies -- mongodb, gridfs-stream...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

Tried 3-4 times since morning fails consistently.

At the same timemeteor run works fine without any issue.

aaronjudd commented 7 years ago

I saw this a few times (on macOS) as well while trying to use the bundle-visualizer and --production. I'm not sure this is Windows (or CLI) specific. I was not running the CLI, just meteor run. Seems like it's been one of those ongoing Meteor issues, that is exacerbated in 1.5. Each time I got this, I killed all Meteor threads and reran successfully.

aaronjudd commented 7 years ago

@jshimko reported this was resolved in https://github.com/reactioncommerce/reaction/issues/2177

The build args he mentions there are setting TOOL_NODE_FLAGS="--max-old-space-size=2048" this is also a suggested fix from the various Meteor issues on this topic. You could try that (and maybe we should bake that in??)

jshimko commented 7 years ago

Yep, try putting that before the reaction command. You could even go a little higher if your machine has plenty available. 

TOOL_NODE_FLAGS="--max-old-space-size=4096" reaction
jshimko commented 7 years ago

Also, for a little more detail...

https://stackoverflow.com/a/42694149/3129944

jshimko commented 7 years ago

@hrath2015 is this still an issue for you after updating to Meteor 1.5.1?

hrath2015 commented 7 years ago

Sorry for delayed response @jshimko It is same. For all fresh install it happens(first time). I close command prompt, open a new one and reaction run to get going. image

bkilrain commented 7 years ago

I'm getting the exact error when running reaction build myCustomImage. Nothing I do can get the image to build... even when running the build on an ec2 box or using docker hub's automated build feature.

phenomenon01 commented 7 years ago

I also getting this error on my mac , I have tried solutions mention here , but no help.

jshimko commented 7 years ago

@bkilrain @phenomenon01 Try doing your docker build with the TOOL_NODE_FLAGS arg...

docker build --build-arg TOOL_NODE_FLAGS="--max-old-space-size=2048" -t myCustomImage .
brent-hoover commented 6 years ago

This is resolved by the workaround of adding the TOOL_NODE_FLAGS args. Closing