1421405 - Errors on exit (Linux): ###!!! [Parent][MessageChannel] Error: (msgtype=0x150083,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv

Status: NEW

(Core :: DOM: Content Processes, defect, P5)

Description

[Jim Avera]

Attachment: Xorg.0.log

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce:

1. Start firefox
2. File->Quit


Actual results:

The following appears on the terminal:

###!!! [Child][MessageChannel] Error: (msgtype=0x42000E,name=PHttpChannel::Msg_DeletingChannel) Channel closing: too late to send/recv, messages will be lost


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


###!!! [Child][MessageChannel] Error: (msgtype=0x2400A8,name=PContent::Msg_ScriptError) Channel closing: too late to send/recv, messages will be lost


###!!! [Parent][MessageChannel] Error: (msgtype=0x150083,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv


###!!! [Child][MessageChannel] Error: (msgtype=0x150001,name=PBrowser::Msg_AsyncMessage) Closed channel: cannot send/recv





Expected results:

Clean exit, without error.

Running on Ubuntu linux 17.04.   Old i7 with older Nvidia graphics.
In case this has something to do with gpu/graphics optimizations, I will attach my Xorg.0.log which I think indicates what kind of driver & hardware are in use on my system.

Comment 1

[Jim Mathies [:jimm]]

Looks like normal shutdown spew. Doesn't interfere with browser use.

Comment 2

[Jim Avera]

There is no such thing as "normal shutdown spew".   

Error messages, even if provably harmless, pollute the user's terminal screen.  And normal users can not know they are harmless.

Yes, shutting down a message-based algorithm is a tricky corner case, as producers have to be told to stop and waited for before shutting down consumers, or similar.   But non-working shutdown should not be waived off as "normal".