Wheelerof4te wrote:It's using 142 MB on my Debian 9 system that's been running for 3 hours straight with casual usage. So yeah, Debian has done something to it, or it doesn't exist in GNOME 3.22.

This bug has existed for 7 years and is now fixed and the fixes are accpeted for GNOME 3.30. There has been some talk about possibly backporting it to 3.28.

It is actually not even a memory leak, but a problem where objects in memory stay there too long (due to how javascript handles objects and how they were linked). They have fixed it by increasing the frequency of garbage collection (by queuing a garbage collection event every time an object is marked for destruction). The price here is that this will cause unnecessary processor work (though not that much) to get the memory to stay down in return. There will likely be better fixes later.