Aggressive Memory Consumption on Fitness page

Bug Reports
1

Hi @david,

Thanks once more for the awesome work on intervals.icu.

I started accumulating a lot of charts on the Fitness page over time. Now, whenever I go back in time more than ~1 year past, my Chrome tab (laptop) keeps crashing. Looking at my Windows Task Manager, this seems to be a memory issue as I run out of available memory.

Can you please help me with the following questions?

  • Can you explain which types of charts consume the most memory?
  • Can you help me troubleshooting the issue?
  • Is there a better way than removing all charts and adding them back 1 by 1 to flag a potential issue? I am currently working on a “run light” fitness tab to allow me going back in time more easily or checking/unchecking charts as needed. But the main pain point with this strategy is constantly changing the date as I alternate between tabs since dates are not attached to single tabs. This also seems to not fully reproduce the issue… loading my “full” run tab from the “light” one seems to avoid the issue altogether.
  • Am I missing something?

Thank you so much and feel free to ask for more details,

Laurent

2

Hi @david,

I still haven’t found a solution to this. Did you get a chance to get a look? Let me know if I can provide anything else to facilitate the investigation/resolution.

Thank you again for all you work!

Laurent

@MedTechCD @Gerald @app4g @Ben in case any of you are able to help. Thanks!

3

I just had a look at your “Run” tab and I think you just have too much going on (too many charts and 4 years worth of data). It works on my M3 Max MacBook Pro but takes a while to load and this is a very fast machine. Memory goes up to 1.1G which is quite a bit but not huge.

All I can really suggest is to try making more tabs and spread the charts out a bit.

4

Hi @david,

Thanks for the recommendation. Since then I had adopted “lighter” tabs and had adopted a 1-year trailing view. That fixed the memory crash on laptop.

I had completely forgotten about this bug report post until I saw this one (Intervals.icu library update complete!). I went back to my previous view (with tons of charts and 4 years of data) and I can confirm it does not crash anymore. The faster (almost instantaneous) rendering is the cherry on top! Great job.

Thank you for the hard work,

Laurent