-
Notifications
You must be signed in to change notification settings - Fork 54
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
Memory leak right after opening IDE #157
Comments
thanks for reporting. Is the provided list of hanging processes a result of you trying it multiple times, or it spawns processes like that with a single run. Also when you shut down VSCode do these processes stay active? |
Hi @kmagiera thanks for looking into it. So far RN IDE seems really promising! The provided list of processes is the result of clicking "Open IDE Panel". So that would be a single run. After dismissing the IDE panel the processes will keep spawning. After closing VSCode the processes will stop spawning and they will automatically stop again. |
Would you be able to double click on any of these in activity monitor to see what's the parent process? The IDE doesn't launch |
I checked on what could be spawning these commands, and it appears like this could be |
Closing this for now as it seems to work fine in other projects and I could not reproduce it in a clean project. |
@kmagiera @leonhh Hello Sir! I've been using the IDE, by the way, amazing. However I'm seeing something quite similar still. After using it several times, I have to go to activity manager and kill tons of node processes that seem to spawn as a result of using it. This gets to a point where every start up it overloads memory if I don't do this. |
I just tested with beta-8 and it seems like there is some sort of memory leak with my project. When I use a newly created project this does not happen. It happens immediately when opening the IDE. It does seem to create a simulator but it keeps hanging on the build step and it consumes all available memory.
npx react-native config
outputapp.config.ts
The text was updated successfully, but these errors were encountered: