Bug 1777914 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

This is a regression introduced by bug 1598164. Especially by these two patches:
https://phabricator.services.mozilla.com/D54322
https://phabricator.services.mozilla.com/D55142
There's a code comment which describes the case when the messages needs to be sent:
```
  // Fire the abort event if there are no outstanding requests. Otherwise the
  // abort event will be fired when all outstanding requests finish.
```
I believe `mReadyState` should not have been added to the check.

This regression has been discovered while we were debugging bug 1775241.

We think that many existing intermittent failures are caused by this issue and probably some shutdown hangs as well.
This is a regression introduced by bug 1598164. Especially by these two patches:
https://phabricator.services.mozilla.com/D54322
https://phabricator.services.mozilla.com/D55142

There's a code comment which describes the case when the messages needs to be sent:
```
  // Fire the abort event if there are no outstanding requests. Otherwise the
  // abort event will be fired when all outstanding requests finish.
```
I believe `mReadyState` should not have been added to the check.

This regression has been discovered while we were debugging bug 1775241.

We think that many existing intermittent failures are caused by this issue and probably some shutdown hangs as well.
This is a regression introduced by bug 1598164. Especially by these two patches:
https://phabricator.services.mozilla.com/D54322
https://phabricator.services.mozilla.com/D55142

There's a code comment which describes the case when the messages needs to be sent:
```
  // Fire the abort event if there are no outstanding requests. Otherwise the
  // abort event will be fired when all outstanding requests finish.
```
I believe `mReadyState` should have been removed from the check.

This regression has been discovered while we were debugging bug 1775241.

We think that many existing intermittent failures are caused by this issue and probably some shutdown hangs as well.

Back to Bug 1777914 Comment 0