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

Reached heap limit Allocation failed - JavaScript heap out of memory #255

Open
saivishwak opened this issue Sep 24, 2022 · 3 comments
Open
Labels
bug Something isn't working

Comments

@saivishwak
Copy link

Describe the bug
Reached heap limit Allocation failed - JavaScript heap out of memory and the webapp doesn't start

To Reproduce
Use clinc-data to start backend server and then after the server is ready (all tasks completed) run the yarn start command in webapp

Webapp started fine after several retries.

Some advices:

  • Please don't use customer data or custom paths.
  • Link to a gist would be appreciated.

Expected behavior
Webapp to start without any memory allocation error without waiting for a long period of time and several webapp restarts

Vesion (please complete the following information):

  • OS: Windows (WSL 2)
  • Azimuth version: 2.3.0

Additional context
Host: 16 GB DDR5 RAM

Screenshot 2022-09-24 151159

@saivishwak saivishwak added the bug Something isn't working label Sep 24, 2022
@gabegma
Copy link
Contributor

gabegma commented Sep 26, 2022

@christyler3030 - any idea what is going on here? I've never experienced this.

@christyler3030
Copy link
Collaborator

@saivishwak - what version of node are you using?

@saivishwak
Copy link
Author

Hi @christyler3030,

Node version - 16.17.1

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
Status: 🆕 New
Development

No branches or pull requests

3 participants