On Jan 6, 10:47 am, Sworddragon <[email protected]> wrote:
> > So SwordDragon, you say you can reproduce these problems. How?
>
> Maybe you missunderstood me, because the reproduction is explained in
> my other posts. Maybe my english acknowledgment is to bad for such
> complex posts.

I think your english is great! But I think you misunderstand what a
test case is.

I need a detailed step-by-step procedure that everyone can apply and
get exactly the same result, and a way to tell that we got the same
result. For example,
1. Use Firebug 1.6a1 in Firefox 3.5.7
2. Open http://getfirebug.com
3. Open Firebug with F12
4. Enable all panels, select the Console panel
5. Reload
6. Check the OS memory
7. Reload
8. Compare the OS memory with step 6 after waiting for 5 seconds.
The result will be no significant increase in memory no matter how
many times you repeat 5-8.

So there is my test which shows that Firebug has no leaks. You repeat
that test. Do you see a different result? If not then do you have a
change to the test which shows a leak?

jjb

>
> I try it to explain it simple:
>
> Just run your firefox with firebug enabled about 1-7 days and do your
> daily requests (like looking for other bug reports on firebug) and
> look at your memory usage sometimes after closing all tabs and
> deleting your cache. You will see a little increased memory usage
> every day. In this time you will got hundred of freezes and this is
> not because an image that is loading in a loop because all contents
> are already loaded (for example i got this freezes permanently with a
> local version of phpMyAdmin and all other sites that i visit).

I'm completely sure you have a problem. But this isn't a test case,
the steps are too vague to reproduce.

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.


Reply via email to