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

Metro Bundler doesn't start and consumes a lot of memory #545

Closed
Inovassist-dev opened this issue Jul 16, 2019 · 7 comments
Closed

Metro Bundler doesn't start and consumes a lot of memory #545

Inovassist-dev opened this issue Jul 16, 2019 · 7 comments
Labels
bug Something isn't working

Comments

@Inovassist-dev
Copy link

Environment

System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
Memory: 2.43 GB / 7.89 GB
Binaries:
Node: 12.6.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.17.3 - C:\Users\xades\AppData\Roaming\npm\yarn.CMD
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
Watchman: 4.9.4 - C:\Users\xades\Documents\watchman\watchman.EXE
IDEs:
Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5692245

Description

When I start my Metro Bundler with react-native start it gets stuck on "Loading Dependency Graph..." and starts to consume a lot of memory...

image

memory

Reproducible Demo

This happens in every project I start in the latest version...

@Inovassist-dev Inovassist-dev added the bug Something isn't working label Jul 16, 2019
@Esemesek
Copy link
Member

This is probably an issue with metro bundler. What version of react-native do you use? Was this issue happening with older versions of react-native?

@thymikee
Copy link
Member

Known issue with latest Node #485 (comment)

@umuterc
Copy link

umuterc commented Aug 6, 2019

I have the same problem when i write react-native run-android it starts and in the middle of the proccess it stucks and using a lot of memory and then i cant even use my mouse my whole computer stucks.Could you find a solution?

@Inovassist-dev
Copy link
Author

After downgrading Node to the latest stable version fixed for me...
Can you run run-android command in verbose mode to see if something pops out?

@umuterc
Copy link

umuterc commented Aug 7, 2019

Thank you i changed the node version to v10.16.2.It is fixed.

@Inovassist-dev
Copy link
Author

You're welcome! 😉

@ghost
Copy link

ghost commented Nov 3, 2020

@Inovassist-dev Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants