Bug 1779540

Summary:	firefox-71.0-8.npgo.fc32 crashes on open tabs
Product:	[Fedora] Fedora	Reporter:	edpil02 <edpil02>
Component:	firefox	Assignee:	Gecko Maintainer <gecko-bugs-nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	0xalen+redhat, anto.trande, gecko-bugs-nobody, jhorak, john.j5live, kengert, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-04 08:08:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description edpil02 2019-12-04 07:55:08 UTC

Firefox crashes as soon as a tab is open .
Delete .mozilla folder and cache does not help.

Message: 

                Gah. Your tab just crashed.
                       We can help!
Choose Restore This Tab or Restore All Crashed Tabs to reload the page/pages.


Backtrace :

[Parent 9640, Gecko_IOThread] WARNING: pipe error (62): Connexion ré-initialisée par le correspondant: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 9640, Gecko_IOThread] WARNING: pipe error (154): Connexion ré-initialisée par le correspondant: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 9640, Gecko_IOThread] WARNING: pipe error (84): Connexion ré-initialisée par le correspondant: file /builddir/build/BUILD/firefox-71.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358

Comment 1 Martin Stransky 2019-12-04 08:08:20 UTC

Dupe of Bug 1778366

You can disable e10s as a workaround (set MOZ_FORCE_DISABLE_E10S=1 or browser.tabs.remote.autostart at about:config)

*** This bug has been marked as a duplicate of bug 1778366 ***