RN 0.60 & Windows 10 Memory leak

[MAKARD]

ReactNative 0.60 didn't start the server on Windows 10. After a long time, all RAM has been used.

React Native version:
System:
OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Memory: 5.98 GB / 15.85 GB
Binaries:
Node: 12.5.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.16.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5522156
react-native: 0.60.0

Steps To Reproduce

1. Get Windows 10.
2. react-native init Project.
3. cd /Project && npm start.

Describe what you expected to happen:
Project starts normally

Actual behavior:
Huge memory leak, unexpected termination

Related to Issue 25551

[react-native-bot]

Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety?

👉 Click here if you want to take another look at the Bug Report issue template.

[louisch]

Can confirm this is also happening on Linux with a freshly created project.

React Native version:
System:
OS: Linux 5.2 Arch Linux undefined
CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Memory: 11.20 GB / 15.58 GB
Shell: 5.7.1 - /usr/bin/zsh
Binaries:
Node: 12.5.0 - ~/.nvm/versions/node/v12.5.0/bin/node
Yarn: 1.16.0 - /usr/bin/yarn
npm: 6.10.0 - ~/.nvm/versions/node/v12.5.0/bin/npm
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.0 => 0.60.0

Steps To Reproduce

1. Create fresh project using npx react-native init <project-name>
2. Start the bundler with npm start

louisch/TestMemoryLeak

[CarlosX4vier]

Same problem here, the computer crashes.

OS: Linux 4.15 elementary OS 5.0 Juno
CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Memory: 5.89 GB / 7.58 GB
Shell: 4.4.20 - /bin/bash

Binaries:
Node: 12.6.0 - /usr/bin/node
Yarn: 1.15.2 - ~/.yarn/bin/yarn
npm: 6.9.0 - /usr/bin/npm
SDKs:
Android SDK:
API Levels: 28
Build Tools: 28.0.3
System Images: android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.3 => 0.60.3
npmGlobalPackages:
react-native-cli: 2.0.1

[fortezhuo]

Same here

System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz
Memory: 1.44 GB / 8.00 GB
Shell: 3.0.2 - /usr/local/bin/fish
Binaries:
Node: 12.6.0 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 28
Build Tools: 28.0.3
Android NDK: 17.1.4828580
IDEs:
Xcode: 10.2/10E125 - /usr/bin/xcodebuild
npmPackages:
react: ^16.8.6 => 16.8.6
react-native: 0.60.3 => 0.60.3
npmGlobalPackages:
react-native-cli: 2.0.1

So.. memory leak occurs on all Operating System (OSX, Linux, and Windows)

[MAKARD]

@hedikasmanto No problems with macOS 10.14.5, seems something with system setup

System:
OS: macOS 10.14.5
CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
Memory: 19.38 GB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.0 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 28, 29
Build Tools: 28.0.3
System Images: android-29 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.0 => 0.60.0
npmGlobalPackages:
react-native-cli: 2.0.1

[fortezhuo]

Hmm. Confused. But while I downgrade to 0.59.x. It back to normal and no memory leak occurs

[hreinhardt]

Seems to be dependent on the node version. I'm getting memory leaks with node v12.6, but not node v10.16.

[MAKARD]

Seems to be dependent on the node version. I'm getting memory leaks with node v12.6, but not node v10.16.

I tried to reproduce the issue with node 10 and 12 (via nvm) on Mac 10.14.5. Still no leaks.

[louisch]

Maybe a watchman issue? I notice all the reports here except @hedikasmanto don't have watchman installed.

I'm not able to install watchman on my setup though, so I can't test this theory out.

[thymikee]

This is a Node >=12.5 issue, see: react-native-community/cli#485 (comment). Feel free to send these report to the Node.js team

[anthonyhumphreys]

are you sure its a >=12.5 issue? I'm on v10.16.3 and getting

Loading dependency graph, done.
transform[stdout]:
transform[stdout]: <--- Last few GCs --->
transform[stdout]:
transform[stdout]: [1085:0x110000000]    96495 ms: Mark-sweep 1386.0 (1425.3) -> 1385.6 (1422.3) MB, 1792.9 / 0.0 ms  (average mu = 0.073, current mu = 0.020) allocation failure scavenge might not succeed

using react-native start - i previously had this issue but fixed with --max_old_space_size=8192 but i can't figure out how to pass args to 'react-native start'