Now that "crashedTabRevived" messages are sent via sendAsyncMessage() from the unload handler we receive those as well when removing a tab with about:tabcrashed loaded. We currently don't expect these messages from a <browser> that lots its <tab> but we should.
Iteration: --- → 40.3 - 11 May
Points: --- → 1
Attachment #8602039 - Flags: review?(wmccloskey) → review+
Any chance of a test for this?
(In reply to Bill McCloskey (:billm) from comment #2) > Any chance of a test for this? This didn't really break anything, the only thing we could add is a test that removes a tab, waits for the final message and then checks that we didn't log any console messages in between. That doesn't feel like we would be testing the issue itself, what do you think?
Sure, seems fine not to test.
You need to log in before you can comment on or make changes to this bug.