>>197
>I tried that (in linux) and it did keep allocating memory (which firefox does anyway for cacheing). Enabling post expansion didn't make a difference to me.
It's different from the normal behavior here. I can get it up to over a hundred megabytes with a few dozen reload alls (Firefox's memory cache is limited here anyway). And it only seems to happen once I enable a feature that changes html code. When I just have the menu with the board list enabled, the leaking is industinguishable from Firefox's usual faggotry.
Do you have a Windows machine available you can try it on? (Or can somebody else reproduce it?)
Maybe the relevant part of the parser function is skipped or doesn't run all the way through when no feature that requires it is enabled?