Profile data is kept directly the on function objects it's associated with. That is, there is an object that represents function |f|, and that object knows (among many other things) that |f| was called N times, and had an min call time of X and a max of Y, etc. When you close the window that defined |f|, the object is destroyed by the js engine, and the profile data goes with it. The workaround is to not close the window that contains the functions you're profiling. Problem is, that's kinda lame. We'll need to come up with a plan for dealing with this, by 1.0. If that plan involves native changes, it'll need to be implemented for 1.0 too.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
If this can be done in script only, I'll shoot for 1.0.1, otherwise it's going to have to get Futured.
Target Milestone: mozilla1.0 → mozilla1.0.1
You need to log in before you can comment on or make changes to this bug.