Skip to content
This repository has been archived by the owner on Apr 7, 2023. It is now read-only.

Build RAM usage remains after turtle build:android finishes #316

Open
5 tasks done
nchrysis opened this issue May 24, 2021 · 1 comment
Open
5 tasks done

Build RAM usage remains after turtle build:android finishes #316

nchrysis opened this issue May 24, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@nchrysis
Copy link

nchrysis commented May 24, 2021

New Issue Checklist

  • Updated turtle-cli to the latest version (yarn global add turtle-cli or npm install --global turtle-cli).
  • I read the Contribution Guidelines.
  • I read docs.expo.io (Managed Workflow > Distributing Your App).
  • I searched for existing GitHub issues.
  • I enclosed the complete output when running turtle, including the stack trace and command used.

Issue Description

After running the turtle-build:android command, the java program remains in RAM and has high memory usage about 5.5GB.
Expected behaviour: after the build command finishes, the java program used to generate the .apk, frees up its memory and exits.
Screenshot_20210524_170023

Command executed

turtle build:android --keystore-path <keystore.jks> --keystore-alias -t apk

Complete output when running turtle, including the stack trace and command used
 The build command completed successfully. 

Environment

Expo CLI 4.4.8 environment info:
    System:
      OS: Linux 5.9 Manjaro Linux
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 14.16.0 - /usr/bin/node
      Yarn: 1.22.10 - ~/.npm-global/bin/yarn
      npm: 7.11.2 - ~/.npm-global/bin/npm
    IDEs:
      Android Studio: 4.2 AI-202.7660.26.42.7351085
    npmPackages:
      expo: ^41.0.0 => 41.0.1 
      react: 16.13.1 => 16.13.1 
      react-dom: 16.13.1 => 16.13.1 
      react-native: https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz => 0.63.2 
      react-native-web: ~0.13.12 => 0.13.18 
    npmGlobalPackages:
      expo-cli: 4.4.8
    Expo Workflow: managed
@nchrysis nchrysis added the bug Something isn't working label May 24, 2021
@Gustavo210
Copy link

same problem, I noticed that it happens on linux and mac but on linux the amount of ram used is exorbitant, easily using about 2 3gb.

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

No branches or pull requests

2 participants