Bugzilla

(In reply to Gabriele Svelto [:gsvelto] from comment #17)
> When it happens the next time can you look up the parent process and kill it with `kill -ABRT <pid>`? That should launch the crash reporter, submit the crash and then let's have a look where it got stuck.

The parent process is not stuck, it exits successfully and Firefox never re-starts.

I confirmed this by launching Firefox from the command-line, without `&` (so that it does not give me back control of the prompt). When I clicked "Restart to update", the process exited and gave me back control of the prompt at that time (and Firefox did not re-start).

The only thing printed on the command line was a bunch of these:

```
###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
```

but these were printed during browsing, but specifically at shutdown time.

In case it matters, there is another Firefox instance (with a different profile) open as well. I haven't paid enough attention recently to see if that's always the case when the issue occurs (historically it wasn't, it used to happen even when only the one instance was running, but that may have changed), but it's been the case the last ~3 times the issue has occurred.

(In reply to Gabriele Svelto [:gsvelto] from comment #17)
> When it happens the next time can you look up the parent process and kill it with `kill -ABRT <pid>`? That should launch the crash reporter, submit the crash and then let's have a look where it got stuck.

The parent process is not stuck, it exits successfully and Firefox never re-starts.

I confirmed this by launching Firefox from the command-line, without `&` (so that it does not give me back control of the prompt). When I clicked "Restart to update", the process exited and gave me back control of the prompt at that time (and Firefox did not re-start).

The only thing printed on the command line was a bunch of these:

```
###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
```

but these were printed during browsing, not specifically at shutdown time.

In case it matters, there is another Firefox instance (with a different profile) open as well. I haven't paid enough attention recently to see if that's always the case when the issue occurs (historically it wasn't, it used to happen even when only the one instance was running, but that may have changed), but it's been the case the last ~3 times the issue has occurred.