Build ID: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101206 Firefox/4.0b8pre Prerequisites: Clean profile This needs a test - page with some heavy content. easier to see the problem Steps: 1. Open http://www.nypost.com 2. Bring up the console CTRL + SHIFT + K 3. Reload nypost.com CTRL + SHIFT + R 4. Close the console CTRL + SHIFT + K quickly, don't wait for nypost to completely reload Behavior: It's easy to observe a significant delay before the web console is dismissed. This would probably be fixed when bug 611789 lands, right?

I witnessed a little bit of delay following those steps, but nothing that painful. I don't know if the behind-the-scenes cleanup work that's being done will help this bug or not.

(In reply to comment #0) > It's easy to observe a significant delay before the web console is dismissed. > This would probably be fixed when bug 611789 lands, right? I doubt it - this is probably network activity doing this. frankly this seems like a WONTFIX or INVALID - but patches are welcome.

(In reply to comment #2) > I doubt it - this is probably network activity doing this. frankly this seems > like a WONTFIX or INVALID - but patches are welcome. It's not really INVALID, because this is UI latency which should not be impacted by what's going on on the network. We can track this, but it's low priority.

I just tried this on my profile and see no latency. However, I am running Adblock and Flashblock. In any case, I agree with Kevin, probably very low priority.

I notice no delay. (tested on Ubuntu Linux) I doubt bug 611789 would fix this issue. The code there doesn't tackle perf aspects, albeit it does some cleanup which may marginally benefit perf. What you may notice is actually just some UI freeze during JS execution, perhaps on nypost.com. I recommend setting this to WFM. What do you think, Kevin?

OK, given that we've tried things out on different OSes and such, I think WFM seems like a reasonable resolution here. We can take a look if this seems to come up again and becomes reproducible.