Ok, it seems i have... tons of leaks ... More than 900 objects. The log, even zipped is too large for google groups.
There are some lines with firebug in it. I will try to understand some of the lines created by my code, but i have nearly no clue about how to do it. Well, at least a challenge ;). Guillaume 2012/2/29 Guillaume Moulin <[email protected]> > Ok, it seems i have... tons of leaks ... > > More than 900 objects. > > I joined the log (185Mo, sic). > > There are some lines with firebug in it. > I will try to understand some of the lines created by my code, but i have > nearly no clue about how to do it. Well, at least a challenge ;). > > Guillaume > > > 2012/2/29 Guillaume Moulin <[email protected]> > >> Will do that tonight. hoping grease monkey will cope with Firefox Nightly. >> >> Guillaume >> >> >> 2012/2/28 Jan Honza Odvarko <[email protected]> >> >>> On Tuesday, February 28, 2012 11:15:50 AM UTC+1, GM wrote: >>>> >>>> Tested yesterday with 1.10a4. >>>> It's way better but there still is a small leak. >>>> Instead of having to restart firefox every 20min or so, it went for 2 >>>> hours before showing signs of slowness. >>>> >>> So we have some progress, good. >>> >>> >>>> I will try to narrow it down tonight as i will do heavy css & markup >>>> editing. >>>> >>> That would be great! >>> >>> I have created a tool (Firefox extension) that can be used to analyzed >>> Cycle Collector graph >>> >>> http://www.softwareishard.com/blog/planet-mozilla/hunting-zombie-memory-leaks-in-firefox/ >>> >>> You can use it to see whether there are zombie documents - i.e. leaks in >>> the CC graph. >>> (example scenario: open a page, open Firebug, execute your str, close >>> the page, find zombie documents or elements in the graph, if there are any >>> -> there is a leak) >>> >>> So, it's the tool offers a simple way to see that your test case is >>> actually producing a memory leak. >>> >>> Honza >>> >>> >>> >>> >>> >>>> >>>> Guillaume >>>> >>>> 2012/2/24 Jan Honza Odvarko <[email protected]> >>>> >>>>> On Friday, February 24, 2012 7:52:12 PM UTC+1, GM wrote: >>>>>> >>>>>> Yes it is. >>>>>> >>>>> OK, good, I fixed one related memory leak this week. It's included in >>>>> 1.10a4 released today. >>>>> >>>>> >>>>>> Even more with Net panel disabled. >>>>>> >>>>> Ideally, what I need is a page the produces leaks if I loaded it. I >>>>> finally have a way (API) how to dynamically examine Cycle Collector graph >>>>> of object (those who are sitting in the memory and shouldn't, >>>>> see >>>>> https://github.com/janodvarko/**ccdump<https://github.com/janodvarko/ccdump> >>>>> ) >>>>> >>>>> All I need are test cases .... >>>>> >>>>> >>>>>> >>>>>> But it just slow the memory leak :(. >>>>>> I still have to reboot the firefox after a while. >>>>>> >>>>>> I used the same method today on an ubuntu 11.10 32bits with firefox >>>>>> "stable" (10.0.2 i think) and latest "stable" firebug. >>>>>> >>>>> >>>>> Please try 1.10a4 >>>>> http://blog.getfirebug.com/**2012/02/24/firebug-1-10a4/<http://blog.getfirebug.com/2012/02/24/firebug-1-10a4/> >>>>> >>>>> Honza >>>>> >>>>> >>>>> >>>>> >>>>>> It's maybe linked to the new web developer tools. >>>>>> >>>>>> Regards, >>>>>> Guillaume >>>>>> >>>>>> 2012/2/23 Jan Honza Odvarko <[email protected]> >>>>>> >>>>>>> On Monday, February 20, 2012 3:13:50 PM UTC+1, GM wrote: >>>>>>>> >>>>>>>> I can't fully verify the test case as i'm at work but : >>>>>>>> >>>>>>>> - open Firefox 10 (new empty profile) >>>>>>>> - install firebug (using the current tab) >>>>>>>> - open facebook page >>>>>>>> - go to a game app (in my case Kingdom of Camelot) >>>>>>>> - open firebug, activate all tabs, activate the xhttp log in the >>>>>>>> console tab >>>>>>>> - reload page >>>>>>>> >>>>>>> >>>>>>> Is it better if you switch off the Console -> Show XMLHttpRequests >>>>>>> option? >>>>>>> >>>>>>> Honza >>>>>>> >>>>>>> -- >>>>>>> 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 >>>>>>> firebug+unsubscribe@**googlegrou**ps.com<firebug%[email protected]> >>>>>>> For more options, visit this group at >>>>>>> https://groups.google.com/**foru**m/#!forum/firebug<https://groups.google.com/forum/#%21forum/firebug> >>>>>>> >>>>>> >>>>>> -- >>>>> 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 >>>>> firebug+unsubscribe@**googlegroups.com<firebug%[email protected]> >>>>> For more options, visit this group at >>>>> https://groups.google.com/**forum/#!forum/firebug<https://groups.google.com/forum/#%21forum/firebug> >>>>> >>>> >>>> -- >>> 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 >>> https://groups.google.com/forum/#!forum/firebug >>> >> >> > -- 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 https://groups.google.com/forum/#!forum/firebug
