Created attachment 198648 [details]
Tabs are not displaying any content (tab crashed message), console is filled with cannot to send/recv messages.
Workaround is to change browser.tabs.remote.autostart to false. Problem is not existing on FF 62
Did you read pkg-message note from ports r480744?
(In reply to Jan Beich from comment #1)
Yes, I set net.local.stream.recvspace=16384 just after upgrade.
And, having the same notice, ESR version of FF works.
I have some random freezes since 63.0.
(In reply to w.schwarzenfeld from comment #3)
> I have some random freezes since 63.0.
On FreeBSD 11.2? Only when Multiprocess Windows (aka Electrolysis) are enabled? Please, describe the freezes in more detail.
Firefox "forgot" some settings after the last updates. After your last comment, I enable electrolyses again. (browser.tabs.remote.force-enable=true I think).
So I have to wait one or two days if this helps.
Firefox freezes again. But I can tell you no reason, or further information (I don't know what's happen).
Sometimes it crashes and coredumps. Sometimes I could destroy the window. But I still can see
four threads in ps auxwww. Sometimes I could kill this threads. Sometimes not and have to log out
I have only for addons (adblock, noscript, colorfultab and video downloadhelper). Don't think this
addon causes this. I also think it is not video related.
Try to get a backtrace from the crashes after building WITH_DEBUG=1. Maybe the issue is not IPC-related. Anyway, I need more data (e.g., "me too" with details) or steps to reproduce.
Workaround for bug 181741 is also undertested. Maybe try applying the commit MFC'd to /stable/11 locally.
Seems it was trivial. "Cleaned up" my profile and for the moment it seems it is ok.
*** Bug 232875 has been marked as a duplicate of this bug. ***
Did anything change after Firefox 64 update?
Not observing this on 12.0-RC3. Probably, we can close this one.