The HUDService adds a DOMNodeInserted handler to the outputNode to detect messages being added to check whether they need to be filtered. That makes all DOM mutations on the chrome document slower than they need to be. It should do the filtering before the element is added to the output node (I realize there may be multiple callers...) rather than relying on a DOM mutation event.

(In reply to comment #0) > The HUDService adds a DOMNodeInserted handler to the outputNode to detect > messages being added to check whether they need to be filtered. That makes all > DOM mutations on the chrome document slower than they need to be. It should do > the filtering before the element is added to the output node (I realize there > may be multiple callers...) rather than relying on a DOM mutation event. This will be easier to do after the console styling output patch is done. One of the side effects of this patch is that all messages will be routed through a common output function. Alternately, we could fix up and land bug 578658.

This is fixed in my patch queue for bug 605621.

Fixed in the patch attached to bug 605621.

mass change: filter on PRIORITYSETTING

mass change: filter mail on BLOCKERSETTING

Kevin: You're abusing the bug severity field. It's not supposed to mirror the release-blocking state.

Dao: sorry about that. I didn't realize that people were relying on that field for other metrics and such.

fixed by landing of patch in bug 605621