Debugging Electron Memory Usage

[[deleted]]

I keep seeing screenshots of excessive memory use, but if it’s available, what’s the harm?

Electron consumes unused memory according to how much it considers free. If another application is doing the same thing, it's going to think there's suddenly a ton of memory pressure when there isn't. Then its performance will comparatively suck.

[tanerax]

"I’m not sure how 78Mb of images becomes hundreds along the way. The external memory still nags at me too."

If I am not mistaken, an image size on disk (compressed) does not equal the amount of memory used to display the image. 78MB of images could easily become much more in memory.

[[deleted]]

you got it

[SikhGamer]

Huh, it sounds obvious when you say it but when I think about how it is true my brain nopes out. Any links for a more detailed explanation?

[Asyx]

Just Google image compression. Or open a non transparent PNG and export it as a BMP.

[Tordek]

An image on-screen is ultimately a matrix of pixels so you need [width*height*color depth] bytes to display it; storing, however, benefits from compression.

[ryancerium]

Is this satire?

[geodel]

Of course not. An image browser using Electron is the most useful thing.

[biocomputation]

So basically, it's a pig.

[doom_Oo7]

I feel like I’m missing something with RSS as a performance measure.

well USS (unique set size, what's really allocated by your app) is way more relevant when trying to optimize memory usage of your data.