Right now nsContentList adds itself as an nsIMutationObserver in ctor and removes in dtor, meaning that even if list is dirty and returns early in mutation observing methods, there are always some virtual calls and state checks. Not observing would mean that mRootNode should probably need to become strong ref.
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.