Memory leaks while navigating

Andrejus

Problem: OJET app consumes memory while navigating within the app, when data is already cached. This problem becomes critical for OJET apps with complex forms, switching from one module to another within OJET app keeps reserving memory, without releasing it - until browser crash.

Test case: sample app and screen recording available on my DropBox: https://www.dropbox.com/sh/5bne0acy63k3vsm/AAARABKUYCtbhugwvlcnXjsQa?dl=0

Steps to reproduce:

1. Download and extract the sample app

2. ojet restore

3. ojet serve

4. Open Task Manager in Google Chrome (assuming you are running sample app in the same browser) and locate the record for the sample app, monitor memory allocation

5. Keep clicking sequentially on Dashboard and Incidents tabs within the sample app to produce navigation event (same as in screen recording), with an interval of 2-3 seconds (make sure UI finishes rendering, before clicking). Repeat clicking 20-30 times

Now notice:

1. Task Manager shows memory increase with each navigation. This should not happen, data is already fetched and is retrieved from the cache

2. Wait for 10-15 minutes after the test, you will see that part of the reserved memory was released, but it never drops to the initial level

3. In the sample app, memory grow amount is not dramatic, but in real complex OJET apps, grow within each navigation is around 100 MB

John 'JB' Brock-Oracle

Just to add a public response here.

We've been working this offline and have found a couple of potential issues which we will try to have fixed in v7.2.0 of JET.

I'll post a final resolution once we have it.

Andrew Bennett

Hi JB,

Just wondering if there is an update on what's happening with this issue. Interested to know a few details on it.

Andy

John 'JB' Brock-Oracle

Hi Andy,

Yes, we identified the area that was leaking and have a fix in place for the 7.2.0 release in a few weeks.

--jb