Firefox ESR tabs crashing on startup
I'm using a Docker container to install Firefox ESR via apt-get and then start a Firefox process using a Node.js script that is also started from the Dockerfile. Unfortunately, I'm unable to view any content on Firefox as I get a string of errors. Furthermore, I've tried Googling these errors to no avail. Here are the commands used to install Firefox ESR:
RUN apt-get update && apt-get -y install firefox-esr RUN mkdir -p /var/run/dbus
I am then using the spawn module from Node.js' child_process module with the following command:
firefox-esr -browser -foreground -width ${width} -height ${height} -safe-mode
Here is the full method used to run firefox-esr
export const firefox = (env: NodeJS.ProcessEnv, width: number, height: number) => spawn('sudo', [
'firefox-esr',
'-browser', '-foreground',
'-width', `${width}`,
'-height', `${height}`,
'-safe-mode'
], {
env,
stdio: [
'ignore',
'inherit',
'inherit'
]
})
The errors I receive in the console are:
[Parent 46, Gecko_IOThread] WARNING: pipe error (69): Connection reset by peer: file /build/firefox-esr-GalmjP/firefox-esr-60.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 342
###!!! [Parent][MessageChannel] Error: (msgtype=0x2D0001,name=PContent::Msg_PBrowserConstructor) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x160069,name=PBrowser::Msg_SynthMouseMoveEvent) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x160001,name=PBrowser::Msg_AsyncMessage) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x160001,name=PBrowser::Msg_AsyncMessage) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x2D0041,name=PContent::Msg_LoadProcessScript) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x16007F,name=PBrowser::Msg_LoadRemoteScript) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x2D0021,name=PContent::Msg_DataStoragePut) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x49001D,name=PHttpChannel::Msg_SetPriority) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x160001,name=PBrowser::Msg_AsyncMessage) Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
###!!! [Parent][MessageChannel] Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
The container is being given 150MB of RAM with a limit of 300MB
Any help would be appreciated! Thanks!
An gyara daga cor-el
All Replies (1)
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.