This Microsoft article - " Preventing Memory Leaks in Windows Applications" - recommends using the "Commit Size" figure in Task Manager. If you want a headache too just try making sense of all of this lot.
Tracking down memory leaks is one of the most difficult things to do in debugging. And if I got that bit wrong I wouldn't be in the least bit surprised.
The supposed usage can include memory being used by shared DLLs but exclude memory allocated to another process but being used by this one. A program can be using less than it's been allocated, and some of its allocation can be in the cache waiting to be freed. The problem seems to be trying to define what memory exactly a program is using - private vs. Send over the paracetamol, you've given me a headache. This has opened a can of worms and sent me off chasing rabbits, to mix metaphors wildly. The whole question of memory usage and memory allocation is one where no two people seem able to agree on what should be measured and how, especially in the context of trying to trace a memory leak. Oh, and the big clue in all this is "Adblock Plus". I need the Before and After figures for this exercise. I would be interested to know which end of that spectrum your FF usage is at. It should be in the range of ~370Mb to ~2Gb. If you have FF (and plenty of RAM!) can you run a little check for me?įirst, open FF and check memory usage ( RAM and VM) Modified - see belowĪnd check the memory ( RAM and VM) that Firefox is using now. It's frames and iframes which are the underlying problem, especially for ABP. but in Firefox that website will break the browser on many older machines. There's one particular website which is being used as a benchmark because it contains 400 iframes (ouch). I'm on a long and tortuous journey through Mozilla, Bugzilla, github, ghacks and the Adblockplus website chasing down the reasons for that Firefox memory leak I referred to in one of the SiteAdvisor/Firefox posts.
0 kommentar(er)
