Commit charge usually means physical memory usage plus page-file usage, working set size means the physical memory usage. Have a read on wikipedia about the difference between commit charge and working set size. However, I agree that there might be as well no connection at all between your security software setup and firefox. I remember many problem reports of users when a previous installed antivirus software was not removed cleanly from the system before installing another product (Norton and McAfee was well-known for troubles of that kind). That's just a guess though since not many people run 3 antivirus guards simultaneously (since everybody recommends against it.) so this problem might not be well documented on the net.
Since some Antivirus software also implement web security features the vast number of antivirus and security software running simultaneously might as well have something to do with your Firefox' consuming too much memory. I accept that there may be some historic confusion in what is running, security wise, but nothing gets through, the system works and though now is probably a very good time for an overhaul, the issue here is FF running daft amounts of RAM.
0 kommentar(er)
