firefox-esr 68.2.0.ESR startup error under Debian GNU/Linux
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: ishikawa, Unassigned)
Details
I am not sure if my problem is Debian GNU/Linux specific or not, but here it goes to share my experience under linux.
firefox-esr 68.2.0.ESR startup error under Debian GNU/Linux
My debian kernel version is:
$ uname -a
Linux ip030 5.2.0-3-amd64 #1 SMP Debian 5.2.17-1 (2019-09-26) x86_64 GNU/Linux
I am using a testing package of Debian. So, that may be one of the reasons of ill-behavior.
I could use the installed Firefox ESR version (not sure which it was) a few days ago.
Symptom:
(1) I upgraded my Debian GNU/Linux packages, and firefox seemed to
updated itself some days ago or yesterday, I am not sure when.
When I tried to run Firefox for the first time after these events by
invoking it from the application menu maybe for the first time in a
few days, Firefox was not usable because any tab including the startup
tab(s) that I wanted to create crashed, and firefox displayed the
error message and offered to close the tab or restore the tab.
Since the tab(s) crashed immediately after startup, if I closed the
tab, Firefox terminated.
If I tried to restore the tabs, this again resulted in the same tab
crashing dialog screen page. There was no way out.
(2) Another bug I noticed is incorrect link in the help dialog.
I get Page not found error when I clicked on the "What's New" link:
HELP -> About Firefox -> What's New link
I get Page not Found error.
The page shown with BIG "Whoops1" message has URL:
https://www.mozilla.org/en-US/und/firefox/68.2.0/releasenotes/?utm_campaign=whatsnew&utm_medium=firefox-browser&utm_source=firefox-browser
If I delete the "/und" part manually and hit return in the URL bar,
I think the correct page s being accessed.
(I am not sure if the incorrect URL is Debian-specific or originated
in the mozilla binary.)
In then accessed page I see clearly the following message. So it IS
the release note.
--- begin quote
Firefox ESR
Release Notes
Release Notes tell you what’s new in Firefox. As always, we welcome
your feedback. You can also file a bug in Bugzilla or see the system
requirements of this release.
Desktop
Android
iOS
Pre-releases
68.2.0
Firefox ESR
October 22, 2019
Version 68.2.0, first offered to ESR channel users on October 22, 2019
--- end quote
Observed ERROR messages:
While the error in (1) was observed, I saw something like the following (quoted/pasted at the end of this comment) in the startup console where I typed /usr/bin/firefox-esr
Possible Workaround ??? :
I found a solution by accident. I have no idea if this works for everybody.
I tried to restart Firefox after disabling plugin, i.e., safe-mode from the firefox tool menu.
This operation failed again and no window was created.
Usually Firefox restart after disabling plugins. But I saw no such
window and there does not seem to be any live firefox process anymore.
ps axg | grep firefox
did not show firefox process.
So, after this, I ran firefox-esr again by typing the command line
this time. To my relief, this time no "tab(s) crashed" error screen
appeared, and I can access google search, for example eventually.
Something, maybe some profile or whatever, was changed for the better
(?) is my best guess.
Just thought to share my experience.
Note; Some error messages that appeared on the command tty window where I
typed firefox-esr to start Firefox.
Error messages during the time when I observed the error (1) above:
$ firefox-esr
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
[Parent 6980, Gecko_IOThread] WARNING: pipe error (104): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 6980, Gecko_IOThread] WARNING: pipe error (103): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Child 7483, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
###!!! [Child][MessageChannel] Error: (msgtype=0x530005,name=PHttpChannel::Msg_Cancel) Closed channel: cannot send/recv
[Parent 6980, Gecko_IOThread] WARNING: pipe error (114): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
###!!! [Parent][MessageChannel] Error: (msgtype=0x1E008F,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x35011D,name=PContent::Msg_DetachBrowsingContext) Closed channel: cannot send/recv
[Parent 6980, Gecko_IOThread] WARNING: pipe error (65): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 6980, Gecko_IOThread] WARNING: pipe error (187): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$ firefox-esr
[Parent 7708, Gecko_IOThread] WARNING: pipe error (109): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 7708, Gecko_IOThread] WARNING: pipe error (51): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
###!!! [Parent][MessageChannel] Error: (msgtype=0x1E008F,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x35011D,name=PContent::Msg_DetachBrowsingContext) Closed channel: cannot send/recv
ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$
(I have no idea if there was any virtual memory issue or something, but if so, firefox would print out memory error message.)
[end of memo]
Reporter | ||
Comment 1•5 years ago
|
||
I filed a bug report to Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944706
There, you can find my apt repository setup.
At the same time, yesterday morning I had a tab crash for the first time in last dozen months or so under Windows 10.
I checked the version of FF
this morning. It is 70.0.1 64-bit. It may be that late versions of FF is more vulnerable to tab crashes before?.
TIA
Comment 2•5 years ago
|
||
Hey ISHIKAWA,
Sorry for the late response. Are you still encountering this crashes?
If yes, can you please provide the crash reports from about:crashes?
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Timea Cernea [:tbabos] from comment #2)
Hey ISHIKAWA,
Sorry for the late response. Are you still encountering this crashes?
If yes, can you please provide the crash reports from about:crashes?
I am not sure if all of below are relevant, but here they go. Some are from Nov 13 and others are from Nov 14.
20a0f407-914a-97b5-7356-3a36d0a6950e 11/14/19, 4:28 AM
52bd4e22-81b6-8e96-556d-0f00f5e0d373 11/14/19, 4:28 AM
23743e72-d241-e8fb-5f9d-d65ec58aa522 11/14/19, 4:26 AM
15ed64c7-5b4c-7913-2391-7e76f6713b73 11/14/19, 4:26 AM
6d4dcbf9-ef7b-e17f-c46e-fd630e0d152a 11/14/19, 4:26 AM
26277fc1-7de3-3d88-e38b-7d240fef563f 11/14/19, 4:26 AM
3a885e24-1ca0-074b-5f3f-cd4271657053 11/13/19, 6:15 PM
68cd3bdd-b6c0-7f4e-1585-b92537c21328 11/13/19, 6:15 PM
4f85fbae-ee4e-beca-16aa-df440fd52543 11/13/19, 6:15 PM
2a91e096-edc4-697e-b234-735aad2d7142 11/13/19, 6:15 PM
09563d55-37e8-6677-23c9-ac3d9addda1d 11/13/19, 6:15 PM
4749dfbc-7d6a-1b83-244d-e6338da8ea06 11/13/19, 6:15 PM
7af60d38-2ba0-8952-007b-1e7adc813a0e 11/13/19, 6:14 PM
1880bce5-3853-d85c-c0cd-597bda2f1f57 11/13/19, 6:14 PM
6f1cdc9a-e9b9-c46d-59e5-82165b5fa265 11/13/19, 6:14 PM
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to ISHIKAWA, Chiaki from comment #3)
(In reply to Timea Cernea [:tbabos] from comment #2)
Hey ISHIKAWA,
Sorry for the late response. Are you still encountering this crashes?
If yes, can you please provide the crash reports from about:crashes?I am not sure if all of below are relevant, but here they go. Some are from Nov 13 and others are from Nov 14.
20a0f407-914a-97b5-7356-3a36d0a6950e 11/14/19, 4:28 AM
52bd4e22-81b6-8e96-556d-0f00f5e0d373 11/14/19, 4:28 AM
23743e72-d241-e8fb-5f9d-d65ec58aa522 11/14/19, 4:26 AM
15ed64c7-5b4c-7913-2391-7e76f6713b73 11/14/19, 4:26 AM
6d4dcbf9-ef7b-e17f-c46e-fd630e0d152a 11/14/19, 4:26 AM
26277fc1-7de3-3d88-e38b-7d240fef563f 11/14/19, 4:26 AM
3a885e24-1ca0-074b-5f3f-cd4271657053 11/13/19, 6:15 PM
68cd3bdd-b6c0-7f4e-1585-b92537c21328 11/13/19, 6:15 PM
4f85fbae-ee4e-beca-16aa-df440fd52543 11/13/19, 6:15 PM
2a91e096-edc4-697e-b234-735aad2d7142 11/13/19, 6:15 PM
09563d55-37e8-6677-23c9-ac3d9addda1d 11/13/19, 6:15 PM
4749dfbc-7d6a-1b83-244d-e6338da8ea06 11/13/19, 6:15 PM
7af60d38-2ba0-8952-007b-1e7adc813a0e 11/13/19, 6:14 PM
1880bce5-3853-d85c-c0cd-597bda2f1f57 11/13/19, 6:14 PM
6f1cdc9a-e9b9-c46d-59e5-82165b5fa265 11/13/19, 6:14 PM
I am no longer seeing the crashes, but the ones above especially the one on Nov 13 must have been them, but my memory is hazy now.
Comment 5•5 years ago
|
||
Sorry for the late response, if you still encounter the hazy memory issue, please create a memory report and post it here.
Here is how to do that:
- Wait until Firefox is consuming a large amount of memory
- Enter about:memory in the URL bar and press enter
- Click "Measure and save" (optionally with "anonymize" checked to hide URLs, although this will likely make it more difficult for us to figure out which site, if any, is causing the leak)
- Save the memory report somewhere
- Attach the report to this bug
Reporter | ||
Comment 6•5 years ago
|
||
(In reply to Timea Cernea [:tbabos] from comment #5)
Sorry for the late response, if you still encounter the hazy memory issue, please create a memory report and post it here.
Here is how to do that:
- Wait until Firefox is consuming a large amount of memory
- Enter about:memory in the URL bar and press enter
- Click "Measure and save" (optionally with "anonymize" checked to hide URLs, although this will likely make it more difficult for us to figure out which site, if any, is causing the leak)
- Save the memory report somewhere
- Attach the report to this bug
Oh, sorry. When I said "my memory is hazy", I was referring to my memory, i.e., my brain (!) :-)
I meant to say "I don't recall very well and I am not 100 % sure that the reports from Nov 13 are the error reports concerning the tab crashes I had reported although I was fairly certain".
The memory in my PC is ECC-type and this hardware worked fine for the last 12 months. :-)
[Unless I have a reliable hardware, it is sometimes very difficult to tell what went wrong with ill-behavior of a large program like TB, especially memory-related issues as you correctly surmized. That is why I have been using ECC-type memory for the PC where I develop patches for TB.]
Thank you for your tips regarding collecting information regarding memory. I will do so when I suspect that the memory leak or memory-related issues are to blame for the bug I observe.
Comment 7•5 years ago
|
||
Hi,
There were no updates regarding this bug for 2 months, will close it as resolved:worksforme but please do re-open it if you encounter this again and also go through the instructions provided in Comment 5.
Comment 8•5 years ago
|
||
Actually, incomplete was the right status here, sorry for the spam.
Description
•