Comment 51 for bug 2050865

I think this is one of those cases where upstream fixed one of the root causes of an assertion failure without actually making the assertion failure impossible. So the fix can be correct, and the crash still happens.

Personally I'd prefer to not declare any assertion failure fixed unless either:
(a) It's been deleted from the code; or
(b) There is definitely only one path to it and that one path has been fixed.

Most likely I think we'll need to keep this bug open and just disassociate it from the upstream fix in 46.1.