[ANGULAR] - Memory use keeps increasing

[rayudu.pasumarthy]

Hi,

We are having some Out-of-Memory crashes with large projects because memory use keeps creeping up over time even when the user is just scrolling around - the memory use keeps going up.

Even on changing projects between 1k tasks to 10k tasks, the memory values keep on increasing even though we destroy the previous project using:

gantt.project?.destroy();

bryntum_memory_increase.png (76.24 KiB) Viewed 221 times

Steps:

1. Open bryntum big dataset example (https://bryntum.com/products/gantt/examples/bigdataset/ )

2. Swap between 1K Tasks tab and 10K tasks tab about 10 times.

3. Notice the change in JS Heap (Developer tools -> Memory)

Even on a single project, only scrolling from the top left of the gantt to the bottom right constantly increases the memory

scroll_memory.png (1.51 KiB) Viewed 221 times

The more attempts on scrolling, the values continue to increase

memory_value_changes.png (103.82 KiB) Viewed 221 times

Are there any other methods available to release the previous objects once they are completed? Can we release the memory of the HTML element tasks after they go out of view?

Regards,
Rayudu

[nickolay]

I don't really observe the behavior you are describing. See the video here: https://streamable.com/02otz1

Perhaps you have some Chrome plugins?

[rayudu.pasumarthy]

Many of our users gain an increase in memory usage throughout the day, even in situations where they logout/login or refresh the page. The memory keeps on increasing.

Please check the attached video below:

memory_increase_on_login_and_refresh.mp4

(5.09 MiB) Downloaded 20 times

1. The memory keeps increasing even though we destroy the gantt. This occurs to all our users that logout and login

2. On page refresh, the memory remains similar to the state that it was previously in

Is there another function to completely flush out all Bryntum Gantt data once the usage has completed?

Thanks,
Rayudu.

[nickolay]

I'll check this scenario soon and get back to you.

[nickolay]

Indeed, it seems destroying the gantt does not free the allocated memory (at least in that example), we'll be fixing this. Ticket created: https://github.com/bryntum/support/issues/8853