Memory leak in frontend?

[nicholascc]

On first look it seems like the line graphs are using a lot of memory, but maybe it's some other element:

Looking into it now.

[nicholascc]

Found 478 detached versions of the graph:

And 2035 detached versions of the market page:

I'm assuming the former is related to the latter. If you have ideas for why this is happening, let me know. Currently looking through the code myself.

[nicholascc]

I am currently most sus of LayerChart but of course that's because I can't easily see into it. :P

Also see a snapshot of the heap:

[Crazytieguy]

Huh, cool. It wouldn't be very surprising to me if the charting library uses a lot of memory when there's a lot of trades, if it's a problem we could try doing candles instead or something. Although are you sure the "Node Count" number is detached copies and not just the amount of html nodes inside the top level element?

[Crazytieguy]

What prompted you to work on this?

[nicholascc]

Oh, it probably is the amount of nodes inside the top level element. And I sort of buy that it’s just the charting library using a lot of memory.

I started working on this because Chrome was lagging on my computer and unable to stream video. I checked Task Manager and found 98% memory usage by Chrome, then checked Chrome Task Manager and found 1.2GB usage for 2 trading bootcamp tabs. Not the wors - other things were using more memory - but still substantial. I thought this was way too high so I ran a memory profile.