> Your description of your browser experience uses words like 'leak' and > 'freeze'. My question is: how can we know the difference between a > 'leak' and simply your app takes a lot of memory to debug? or between > a 'freeze' and your app takes a lot of CPU to debug?
As i sayed i have tested firefox with firebug enabled and after this i have tested it with firebug disabled. Without firebug firefox is not using more than 100 MB of memory and with firebug enabled firefox uses ~200 mb of memory (just after the seventh day). And this with all tabs closed and a cleared cache (the cache control in firefox is set to automatic). Firefox was using every day a little bit more of memory but only with firebug enabled and firefox was freezing every day a little bit more only with firebug enabled too. This seems for me to a memory leak this causes firebug to freeze the browser sometimes. This bug is every time reproduceable (I'm using Windows XP Professional SP3 if it is necessary) and now some programmers can try to analyze this problem to see if this is really a memory leak.
-- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
