Earlier quoted context omitted.
Or apps that have no business being webapps, but somehow are. When a chat and video/audio call client take 4GB all by itself...
It's bloat caused by stuff like Electron, and people choosing to write desktop apps in HTML + JavaScript/TypeScript + some framework. If people even used a framework like Qt (a really mature and well-maintained desktop framework the favored framework of KDE Plasma, etc.), their memory usage would be so much lower. (I'm not counting the memory used by Qt's shared .so / dynamic library files.)
While the "web everything" trend is definitely responsible for a lot of the bloat, it is upon closer inspection not the whole story. For example, I remember various "AJAX chat" clients were quite popular around the turn of the century, worked in a browser like IE5 on a system with probably 64-128MB of RAM and a single core Pentium II/III, and you could also do other things like listen to music, play flash games, or read other sites at the same time. Those clients loaded relatively quickly over connections with bandwidth measured in KBps, and I don't recall much in the way of complaints about their resource usage.