Created attachment 431415 [details] [diff] [review]
I'm utterly surprised, but the nsISupportsHashKey implementation actually addrefs/releases its key value when used. Simple fix.
Comment on attachment 431415 [details] [diff] [review]
We're code frozen on 220.127.116.11 and 18.104.22.168, so moving these to the next version.
This will need to land and bake on trunk, first.
Please don't remove the "needed" part from the blocking1.9.2/1.9.1 flags. That means something to drivers and should be left alone.
I'm guessing that was an accident ... /me shakesfist at bugzilla!
Is there anything for QA to verify with this bug? I suspect not.
(In reply to comment #7)
> Is there anything for QA to verify with this bug? I suspect not.
Yeah, not really. I just magically hit it one day... It requires precise timing.