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:
Go to 'Test'
Click on 'Create Test'
Scroll to 'Upload CSV'
Upload a CSV of say 30MB
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
Describe the bug We see the following errors while running extensive tests
To Reproduce Steps to reproduce the behavior:
Expected behavior No memory exhaustion from running aggressive tests suit
Version:
Additional context Maybe provide the ability to override the max_old_space_size with something like