If you post your issue to FireRainbow, please add the backlink here, so we can refer to it. Thanks.
Sebastian On Friday, February 1, 2013 10:08:05 AM UTC+1, Gruewo wrote: > > Looks like FireRainbow is the responsible addon here... since I could not > reproduce the leaking of large strings without it. > > Thus I will take this to the FireRainbow author instead. > > thanks for your help > > On Wednesday, January 23, 2013 5:33:04 PM UTC+1, Gruewo wrote: >> >> > Was this after having disabled Firebug? >> yes as noted in $SUBJECT, all using that small Firefox dropdown button in >> my Navigation bar. >> >> I did notice that disabling Firebug while on a tab where it is not active >> (or just all others?) lets the other tabs persist somewhere, which was very >> noticeable since the source code was visible in the Firefox about:memory >> listing. >> (this was not the case above tough) >> >> I attached a cycle-collector-analyzer log file, in case it helps >> somebody... >> >> Since i now use 3 addons binary searching for the guilty one should be >> possible :) >> > -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
