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

React Native 0.60.5 fails to launch and memory goes through the roof #55

Closed
robertherber opened this issue Aug 15, 2019 · 3 comments
Closed
Labels
bug Something isn't working help wanted Extra attention is needed workaround available A workaround is available in the issue's comments

Comments

@robertherber
Copy link

Seems like this library works when running React Native but only when the debugger is attached - which I think implies it has to do with the JavaScript engine (when attaching the debugger it runs V8). It goes for both iOS and Android - on the device and simulator.

It launches the app - succeeds in running decent amounts of JavaScript code i can tell from the logs - but fails to render. Memory consumption goes through the roof during this process as well (after about a minute my app was consuming almost 10gb of memory).

It doesn't render the library completely unusable with RN but it bugs me to have to manually comment the whole library out when I want to run it without an attached debugger - which is usually the case since it has some heavy performance implications.

@robertherber
Copy link
Author

I found a workaround that I'll use for now. There is global to determine whether RN is running in the Chrome Debugger global.__RCTProfileIsProfiling, so I'm disabling it otherwise:

if (__DEV__ && global.__RCTProfileIsProfiling) {
    const whyDidYouRender = require('@welldone-software/why-did-you-render');
    whyDidYouRender(React);
}

@vzaidman vzaidman added bug Something isn't working help wanted Extra attention is needed workaround available A workaround is available in the issue's comments labels Sep 9, 2019
@nonewcode
Copy link

nonewcode commented May 12, 2020

Experiencing the same issue. Works fine on first load but after fast refresh tries to kick in, the app memory usage goes 1000mb+ and the simulator has to be force closed. v0.62.2

@vzaidman
Copy link
Collaborator

vzaidman commented Feb 5, 2021

re-open if it still happens

@vzaidman vzaidman closed this as completed Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed workaround available A workaround is available in the issue's comments
Projects
None yet
Development

No branches or pull requests

3 participants