For which issue? The page in question is loading lots of different (from the browser's point of view) images. They won't be released until sometime later (in

For which issue? The page in question is loading lots of different (from the browser's point of view) images. They won't be released until sometime later (in particular, for Gecko until after GC runs on the style data structures). So I would expect memory usage to grow here here until said GC happens, then drop, then grow again, etc. While the images are live, they're stored on the X server, because that's where they need to be drawn; in many cases this will just place them directly into the graphics memory. There _are_ existing Gecko bugs on trying to reduce X server resource usage by dynamically deciding which images to store in the client and which on the server... The bugs are mostly motivated by thin client setups where the X client actually has a lot more in the way of hardware resources than the X server does. Of course those are high-latency X setups (compared to your typical desktop), which makes storing the images you really need on the server all the more important.