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

Nodejs memory allocation failure while running extensive tests suite #594

Open
Ebaneck opened this issue Apr 8, 2022 · 0 comments
Open

Comments

@Ebaneck
Copy link

Ebaneck commented Apr 8, 2022

Describe the bug
We see the following errors while running extensive tests

<--- Last few GCs --->

[1:0x55a454edb000]     3359 ms: Mark-sweep 168.9 (193.5) -> 168.6 (208.0) MB, 30.0 / 0.0 ms  allocation failure GC in old space requested
[1:0x55a454edb000]     3387 ms: Mark-sweep 168.6 (208.0) -> 168.6 (176.5) MB, 28.0 / 0.0 ms  last resort GC in old space requested
[1:0x55a454edb000]     3413 ms: Mark-sweep 168.6 (176.5) -> 168.6 (176.5) MB, 26.4 / 0.0 ms  last resort GC in old space requested

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Test'
  2. Click on 'Create Test'
  3. Scroll to 'Upload CSV'
  4. Upload a CSV of say 30MB
  5. Run aggressive tests

Expected behavior
No memory exhaustion from running aggressive tests suit

Version:

  • Predator: [1.6.2]
  • Predator-runner [1.6.1]
  • Database [MYSQL]
  • Env [Kubernetes]

Additional context
Maybe provide the ability to override the max_old_space_size with something like

ENV NODE_OPTIONS=--max_old_space_size=4096
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

No branches or pull requests

1 participant