Bug 1742677 Comment 40 Edit History

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

Original comment by
on 
[Here](https://treeherder.mozilla.org/logviewer?job_id=374716395&repo=mozilla-central&lineNumber=15751) I read:

``` 
FATAL ERROR: AsyncShutdown timeout in profile-before-change Conditions: [
 {"name":"ContentParent: id=7f25d516f900","state":{"remoteTypePrefix":"prealloc"},
  "filename":"/builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp",
  "lineNumber":3589,"stack":["resource://gre/modules/nsAsyncShutdown.jsm:addBlocker:162"]},
 {"name":"ContentParent: id=7f25d2f95500",
  "state":{"remoteTypePrefix":"prealloc"},
  "filename":"/builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp","lineNumber":3589,
  "stack":["resource://gre/modules/nsAsyncShutdown.jsm:addBlocker:162"]}
] 
At least one completion condition failed to complete within a reasonable amount of time. Causing a crash to ensure that we do not leave the user with an unresponsive process draining resources.
```

This is a manifestation of a double shutdown blocker for the same `ContentParent`. That alone should not cause hangs, but there are also some possible races around the shutdown blockers. Bug 1764251 might help here to some extent.
Revision 1 by
on 
[Here](https://treeherder.mozilla.org/logviewer?job_id=374716395&repo=mozilla-central&lineNumber=15751) I read:

``` 
FATAL ERROR: AsyncShutdown timeout in profile-before-change Conditions: [
 {"name":"ContentParent: id=7f25d516f900","state":{"remoteTypePrefix":"prealloc"},
  "filename":"/builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp", "lineNumber":3589,
  "stack":["resource://gre/modules/nsAsyncShutdown.jsm:addBlocker:162"]},
 {"name":"ContentParent: id=7f25d2f95500",
  "state":{"remoteTypePrefix":"prealloc"},
  "filename":"/builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp","lineNumber":3589,
  "stack":["resource://gre/modules/nsAsyncShutdown.jsm:addBlocker:162"]}
] 
At least one completion condition failed to complete within a reasonable amount of time. Causing a crash to ensure that we do not leave the user with an unresponsive process draining resources.
```

This is a manifestation of a double shutdown blocker for the same `ContentParent`. That alone should not cause hangs, but there are also some possible races around the shutdown blockers. Bug 1764251 might help here to some extent.
Revision 2 by
on 
[Here](https://treeherder.mozilla.org/logviewer?job_id=374716395&repo=mozilla-central&lineNumber=15751) I read:

``` 
FATAL ERROR: AsyncShutdown timeout in profile-before-change Conditions: [
 {"name":"ContentParent: id=7f25d516f900","state":{"remoteTypePrefix":"prealloc"},
  "filename":"/builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp","lineNumber":3589,
  "stack":["resource://gre/modules/nsAsyncShutdown.jsm:addBlocker:162"]},
 {"name":"ContentParent: id=7f25d2f95500",
  "state":{"remoteTypePrefix":"prealloc"},
  "filename":"/builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp","lineNumber":3589,
  "stack":["resource://gre/modules/nsAsyncShutdown.jsm:addBlocker:162"]}
] 
At least one completion condition failed to complete within a reasonable amount of time. Causing a crash to ensure that we do not leave the user with an unresponsive process draining resources.
```

This is a manifestation of a double shutdown blocker for the same `ContentParent`. That alone should not cause hangs, but there are also some possible races around the shutdown blockers. Bug 1764251 might help here to some extent.

Back to Bug 1742677 Comment 40