Skip to content

Conversation

vineetbambah
Copy link

Related Issue
Fixes #775

Description of Changes
I ran into the issue of not being able to build the repository for testing a few days back for which I myself added this issue to the issue board.
I tried to fix this issue on my own and realized that it was a nodejs issue. v8 engine by default has a cap of 2 GB which was overflowing and I added the NODE_OPTIONS to increase the assigned memory for that particular subprocess.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • New example
  • Test improvement

Testing
I initially ran the build process which lead to it being failed.
image
After checking the nodejs memory usage the issue was apparent and I went on to globally set the memory assigned to nodejs 4gb which fixed the issue.
After setting the environment variable there is a layer of abstraction that a new contributor doesn`t have to face to contribute.

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have run my code against examples and ensured no errors
  • Any dependent changes have been merged and published in downstream modules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Error while running build of heap limit allocation failed
1 participant