[FOLIO-2654] BigTest terminates execution during source code re-compiling due to memory leaks Created: 22/Jun/20  Updated: 08/Dec/21  Resolved: 08/Dec/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: TBD
Reporter: Maxim Didenko Assignee: Anton Emelianov (Inactive)
Resolution: Won't Do Votes: 0
Labels: bigtest
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screen Shot 2020-06-22 at 14.40.37.png    
Sprint:

 Description   

Overview:
During development in ui-circulation I've faced with annoying issue of BigTest which leads to constant restart of testing command due to memory leaks during re-compiling of source code.

Steps to Reproduce:

  • run tests in ui-circulation
  • after tests will pass pick one describe and add .only to it in order to run only selected test suite (or any other action which will lead to tests re-run)

Expected Results:
Tests will re-run for selected test suite.

Actual Results:
Tests run will be terminated because of memory leak.

Additional information
OS: Mac OS Mojave 10.14.6
RAM: 32 GB
CPU: 2.3 GHz Intel Core i9
Browser: Chrome Version 83.0.4103.106 (Official Build) (64-bit)



 Comments   
Comment by Anton Emelianov (Inactive) [ 22/Jun/20 ]

Zak Burke, Sobha Duvvuri, Viktor Soroka I think you had similar problem for other modules. Any suggestions how to resolve it in this case?

Comment by Zak Burke [ 22/Jun/20 ]

Short version: Node is memory hog; allocate more either overall with something like

export NODE_OPTIONS="--max-old-space-size=4096 $NODE_OPTIONS"
yarn test

or for this one command specifically with something like

NODE_OPTIONS="--max-old-space-size=4096 $NODE_OPTIONS"; yarn test

Your screenshot shows a problem with node running out of memory, not BigTest (Chrome). We recently saw the same thing in ui-users and some other UI apps; details at FOLIO-2638 Closed . It isn't clear exactly what changed recently (one big change in the last ~month was migrating from react-intl v2 to v4 so that's a suspect). CI boxes have 32GB RAM, we were "only" allocating 2GB to node. Given that we could easily, and with zero cost, throw RAM at the problem and make it go away, we decided it was not worth further investigation at this time even though we would really like to know why this suddenly changed.

Comment by Zak Burke [ 22/Jun/20 ]

FWIW, I cannot duplicate this problem locally in ui-circulation, even with

NODE_OPTIONS="--max-old-space-size=1024 $NODE_OPTIONS"; yarn test

MacOS 10.14.6 (Mojave) with Node 12.14.0.

Comment by Ann-Marie Breaux (Inactive) [ 30/Nov/21 ]

Hi Anton Emelianov Which team should be assigned to this? It seems like it should move to the FAT project, and be assigned to a dev team. Could you review it? Thank you!

Comment by Anton Emelianov (Inactive) [ 07/Dec/21 ]

Zak Burke, Any objections to closing this ticket?

Comment by Zak Burke [ 08/Dec/21 ]

We are migrating away from BTOG and hence will not put effort into resolving this issue or others like it.

Generated at Thu Feb 08 23:22:16 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.