When I enable firefox electrolysis (aka e10s) browser-internal pages such
as about:config, about:support, and about:addons, load, but nothing
actually on the web will load -- the progress bar goes all the way across
and just as the page appears to be parsing, TAB-CRASH, with the offer to
(try to) reload the page (which fails the same way).
This is regardless of whether I'm running with all extensions (which I've
spent quite some time on weeding out and replacing the non-e10s-
compatible ones, they're all reported compatible with multiprocess now)
enabled, all disabled, in safe mode, even after a firefox refresh.
I'm running the packages direct-downloaded and user installed (as opposed
to system install or normal gentoo build and install) from Mozilla, so
it's not a build error on my end.
I've been working on this for awhile, first trying the force-enabling
back on firefox 50 or so, then trying in safe mode and "refreshed" with
51 and now 52, and only just last nite getting the last incompatible
extension removed, so now it's getting frustrating as I have to force-
DISABLE it now, because otherwise I can't browse! Earlier this morning I
tried the beta (53b6) as well -- same problem.
Firefox works fine in single-process mode, tho of course if one tab
blocks that tends to freeze the whole thing, as could be expected in
single-process mode.
I'm wondering if the problem is firefox trying to use some sort of exotic
IPC method I don't have enabled in the kernel or something, since it only
appears to be a problem with e10s, not single-process.
Running firefox from a terminal window, this is the error I get:
[Parent 8379] WARNING: pipe error (89): Connection reset by peer: file /
home/worker/workspace/build/src/ipc/chromium/src/chrome/common/
ipc_channel_posix.cc, line 346
###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0085,name=PBrowser::Msg_Destroy) Channel error: cannot send/
recv
Seeing the ipc_channel_posix.cc thing, I tried enabling
CONFIG_POSIX_MQUEUE in my kernel -- no luck.
To check to see if it's enabled, type about:support in the address bar,
then check the first section, applications basics, under multiprocess
windows. n/m where n is 0 is no, should have a reason. m appears to be
the number of windows so n/m where both numbers are equal and positive
indicates it's enabled for all windows.
Just having others confirm it's working for them, along with the firefox
version they're running and whether it's the mozilla binary or gentoo
build, would give me more info than I have now.
Meanwhile, for those who want to play with it and need further
information:
https://wiki.mozilla.org/Electrolysis
For me tho it was the browser.tabs.remote.autostart2 and force-enable
settings (the latter of which I had to create myself, not just toggle).
Be sure you've backed up your profile, tho, just in case. It should be
located in ~/.mozilla/firefox or similar. Even tho I couldn't get to the
web I could still get to about:config to reset things, but being able to
replace the broken testing config with a normal backup in case things get
too out of hand is definitely nice. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
as about:config, about:support, and about:addons, load, but nothing
actually on the web will load -- the progress bar goes all the way across
and just as the page appears to be parsing, TAB-CRASH, with the offer to
(try to) reload the page (which fails the same way).
This is regardless of whether I'm running with all extensions (which I've
spent quite some time on weeding out and replacing the non-e10s-
compatible ones, they're all reported compatible with multiprocess now)
enabled, all disabled, in safe mode, even after a firefox refresh.
I'm running the packages direct-downloaded and user installed (as opposed
to system install or normal gentoo build and install) from Mozilla, so
it's not a build error on my end.
I've been working on this for awhile, first trying the force-enabling
back on firefox 50 or so, then trying in safe mode and "refreshed" with
51 and now 52, and only just last nite getting the last incompatible
extension removed, so now it's getting frustrating as I have to force-
DISABLE it now, because otherwise I can't browse! Earlier this morning I
tried the beta (53b6) as well -- same problem.
Firefox works fine in single-process mode, tho of course if one tab
blocks that tends to freeze the whole thing, as could be expected in
single-process mode.
I'm wondering if the problem is firefox trying to use some sort of exotic
IPC method I don't have enabled in the kernel or something, since it only
appears to be a problem with e10s, not single-process.
Running firefox from a terminal window, this is the error I get:
[Parent 8379] WARNING: pipe error (89): Connection reset by peer: file /
home/worker/workspace/build/src/ipc/chromium/src/chrome/common/
ipc_channel_posix.cc, line 346
###!!! [Parent][MessageChannel] Error:
(msgtype=0x2C0085,name=PBrowser::Msg_Destroy) Channel error: cannot send/
recv
Seeing the ipc_channel_posix.cc thing, I tried enabling
CONFIG_POSIX_MQUEUE in my kernel -- no luck.
To check to see if it's enabled, type about:support in the address bar,
then check the first section, applications basics, under multiprocess
windows. n/m where n is 0 is no, should have a reason. m appears to be
the number of windows so n/m where both numbers are equal and positive
indicates it's enabled for all windows.
Just having others confirm it's working for them, along with the firefox
version they're running and whether it's the mozilla binary or gentoo
build, would give me more info than I have now.
Meanwhile, for those who want to play with it and need further
information:
https://wiki.mozilla.org/Electrolysis
For me tho it was the browser.tabs.remote.autostart2 and force-enable
settings (the latter of which I had to create myself, not just toggle).
Be sure you've backed up your profile, tho, just in case. It should be
located in ~/.mozilla/firefox or similar. Even tho I couldn't get to the
web I could still get to about:config to reset things, but being able to
replace the broken testing config with a normal backup in case things get
too out of hand is definitely nice. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman