On Jan 6, 9:33 am, Brian Di Palma <[email protected]> wrote: > I simply restart FF. Honestly, Firebug leaks, but the effort required to fix > these issues > would probably be large. I might be wrong but I doubt the Firebug devs are > going to try and fix leaks and I don't blame them as it's a massive > time sink.
I appreciate your attitude. I've worked on bug reports for Firebug memory problems many times. A couple of times I've found and fixed a problem. But the cost/benefit ratio is way out of whack. For some reason memory problems in particular are reported with great indignation and very little in the way of facts. I have to go back and forth for a long time to get a test case. Then lots of times the problem is actually in the application, eg it loads images in a loop or something. If I find and fix a bug, I never recall anyone verifying that Firebug was better for them afterwards. But I don't want anyone to take this as a sign I would not try again. Rather it's the opposite: if anyone wants to put the effort into a test case for a memory (or CPU problem), I'll work on it right away. I just don't to complain about leaks then not follow up with facts. So SwordDragon, you say you can reproduce these problems. How? 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.
