Memory leak when going from compress screen to home screen

[suiyuex]

I don't know this is whether or not a bug
once start compress image process will greatly improve memory usage

any solution can reduce memoery usage or not?

as you can see I just opened the website
the tab take about 30mb of memory

When I upload a image about 1.8m, the memory is straight up, and then wait for compress done (using default options)
the memory is about 800mb
and then i close the website image editor, the memory is about 350mb usage, and cant no longer reduce

this is right or not? and there is a way to solve this or not? thank you guys

[jakearchibald]

and then i close the editor

Do you mean closing the tab, or going back to the home screen?

[suiyuex]

@jakearchibald sorry, i am not clearly described, close the editor is close the image editor
this here

and i want to know the memory usage is normal? thanks.

[jakearchibald]

I can recreate this by:

1. Go to squoosh.app
2. Open the red panda image
3. Click the X to go back to the homescreen
4. GOTO 2

GPU memory usage increases by 100-200mb each time.

It doesn't happen when just changing compression settings, so I suspect it's related to the creation of <canvas>. It could be our bug, or Chromium.

[suiyuex]

Thanks for solving my doubts

[jakearchibald]

I couldn't recreate the issue in a simple reduced way (https://static-misc-3.glitch.me/canvas-memory-test/), so my gut feeling is the memory leak is our fault rather than chrome's.

[suiyuex]

I can recreate this by:

1. Go to squoosh.app
2. Open the red panda image
3. Click the X to go back to the homescreen
4. GOTO 2

GPU memory usage increases by 100-200mb each time.

It doesn't happen when just changing compression settings, so I suspect it's related to the creation of <canvas>. It could be our bug, or Chromium.

the 3 step is go back to the homescreen or go back to the page root route? im confused

[jakearchibald]

"Click the X" (the one in the top-left of your screenshot)

I'm tracking down memory leaks now…

[jakearchibald]

PR #1054

[jakearchibald]

Thanks for filing this issue! It identifed issues in both Squoosh and Chrome.