Open Bug 1783512 Opened 2 years ago Updated 6 months ago

BlockShutdown : ShutDownProcess Warning messages

Categories

(Core :: Graphics, defect, P3)

Firefox 104
defect

Tracking

()

UNCONFIRMED

People

(Reporter: vincentvikram, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0

Steps to reproduce:

~$ ~/Downloads/firefox/firefox &

Actual results:

[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb25e6f7f00 - BlockShutdown: CanSend.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3595
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb25e6f7f00 - ShutDownProcess: Sent shutdown message.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1799
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2773aa600 - BlockShutdown: CanSend.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3595
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2773aa600 - ShutDownProcess: Sent shutdown message.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1799
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2562d7400 - BlockShutdown: CanSend.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3595
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2562d7400 - ShutDownProcess: Sent shutdown message.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1799
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb259369600 - BlockShutdown: CanSend.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3595
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb259369600 - ShutDownProcess: Sent shutdown message.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1799
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb25e6f7f00 - ShutDownProcess: Closing channel.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1834
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb25e6f7f00 - RemoveShutdownBlockers: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3697
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2773aa600 - ShutDownProcess: Closing channel.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1834
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2773aa600 - RemoveShutdownBlockers: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3697
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2562d7400 - ShutDownProcess: Closing channel.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1834
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb2562d7400 - RemoveShutdownBlockers: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3697
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb259369600 - ShutDownProcess: Closing channel.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:1834
[Parent 2573, Main Thread] WARNING: ContentParent: id=7fb259369600 - RemoveShutdownBlockers: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3697

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Content Processes' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Content Processes
Product: Firefox → Core

While the browser is functional, I should have added these messages that keep echo'ing on the terminal as well:
~$ ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_14
ATTENTION: default value of option mesa_glthread overridden by environment.
libva info: va_openDriver() returns 0
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_14
...
<repeat>

Sounds like it's trying to shut down the processes but is blocked and thus had to kill them forcefully, and the reason is probably what's in comment #2.

Component: DOM: Content Processes → Graphics

Andrew, can you see if you can replicate this on Linux?

Severity: -- → S3
Flags: needinfo?(aosmond)
Priority: -- → P3

Possibly related to the analogous problem in Thunderbird in Arch Linux: bug 1788599

The messages as such from comment 0 and bug 1788599 are not indicating any problem. We might want to classify them as INFO, though. A problem would be reported as a shutdown hang crash.

Not sure if there is any relation with the messages from comment 2 here.

The msgs from comment 2 appear when watching Netflix. The msgs in comment 0 appear either way even with latest beta build.

The messages are of course useful information, but at the cost of possible delayed shutdown time, at least in the case of Thunderbird, which may be less acceptable if shutdown is extended by many seconds? I the case of Firefox the shutdown is not delayed noticeably in my tests, but Thunderbird is delayed, so possibly the delay in the case of the latter is due to difference in implementation.

(In reply to Mike Cloaked from comment #8)

The messages are of course useful information, but at the cost of possible delayed shutdown time, at least in the case of Thunderbird, which may be less acceptable if shutdown is extended by many seconds? I the case of Firefox the shutdown is not delayed noticeably in my tests, but Thunderbird is delayed, so possibly the delay in the case of the latter is due to difference in implementation.

The messages themselves should not have any noticeable performance impact. Assuming that you see this with Thunderbird beta 105, could you check if dom.abort_script_on_child_shutdown has any impact? What is it's default value in Thunderbird?

I switched dom.abort_script_on_child_shutdown to True in the config editor, and it still takes the same 8 or so seconds to shut down, and the console messages after thunderbird 105 shuts down are now:

[Parent 3002, Main Thread] WARNING: ContentParent: id=7f7991e69700 - BlockShutdown: NotifyImpendingShutdown.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3626
[Parent 3002, Main Thread] WARNING: ContentParent: id=7f7991e69700 - BlockShutdown: RequestContentJSInterrupt.: file /builds/worker/checkouts/gecko/dom/ipc/ContentParent.cpp:3632

I have now switched dom.abort_script_on_child_shutdown back to the default 'false'.

With recent beta 117.0b3 currently as well as the previous few betas Thunderbird on my systems now shuts down significantly faster than earlier versions. One of my systems has Thunderbird shut in a couple of seconds, and the slowest in about 8 seconds. It does seem that once Thunderbird is running time needs to be allowed for the initial sync before attempting to close down again, or the shutdown does take longer. But a significant improvement compared to versions from a year or so back.

Flags: needinfo?(aosmond)
You need to log in before you can comment on or make changes to this bug.