On Apr 22, 8:26 pm, demongloom <[email protected]> wrote: > Memory profiler is a great and long awaited feature! > > 1. Any way to call memory profiler from js. Like > console.memoryProfile() ?
Oh that's a good idea! If you open a bug report I bet we'd do it for a3. http://code.google.com/p/fbug/issues/list > 2. Where I can find any explanation about memory profiler columns? > What each mean, where is leak, where is not. The top half with the the columns are data out of Firefox. You can guess from the column headings as well as we can. I guess you can read Firefox source to learn more. We hope to learn more from feedback. The bottom half, Object Added, is a delta. When you click the button, we mark all the objects. Then you do some event, and click again: we show you the delta. You need to decide if the delta is a leak or just normal operations. Think of this like a breakpoint debugger or a console.log() line: you do an operation and you get a screen full of values or a line of a log. You know the operation and you know what to expect. If you see something you don't expect, investigate. By the way we know the delta is incomplete. So we need to hear that this feature is worth finishing. The remaining cases are all harder and we don't want to fix them if no one will ever use it. jjb > > Thanks. > > On Apr 22, 5:34 pm, Jan Honza Odvarko <[email protected]> wrote: > > > > > > > > >http://blog.getfirebug.com/2011/04/22/firebug-1-8a2/ > > > 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 [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
