On Jan 8, 2:51 pm, Sworddragon <[email protected]> wrote: > > So far I see no evidence of a memory leak. In your machine you have > > lots of memory taken in the exotic case of tens of thousands of > > reloads. Also in you see lots of memory taken for manual refreshes > > over 7 days. Still the question remains as to the cause of your > > problems. So far we have no way to know if the problem is a Firebug > > memory leak. The fact that the problem disappears when you disable > > Firebug does point to Firebug as being involved. But until we have a > > test case that shows the problem on my machine I can't help you. > > I don't know why you aren't willing to make just one longer test. You > must only one time make my test with 20000 reloads (on my processor it > needs ~1 hour) if the script panel is selected
For two reasons: 20,000 reloads is not realistic and 1 hour is not practical for fixing a memory bug. I really appreciate your efforts. But we need either a more realistic test case or a faster one. I know you are convinced there is a problem, but Firebug has lots of problems. So far the information looks like this problem is not very significant. I'm sorry you have to restart Firefox every few days, but really it's not such a big cost for using Firebug. I think it makes more sense for me to work on changing Firebug so users don't have to reload to debug. Then any memory increase on reload won't matter. If you want to do more experiments I will make more suggestions. First I would suggest you check that the script panel is truly related to the problem. Check another panel, eg HTML and Console. If the memory increase only happens when the Script is selected, then try the script-limiter, the small menu on the tool bar that says "All". Another kind of change is to increase the HTML (by 10x) or the scripts. jjb
-- 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.
