Re: Firefox and the broken about:login, a temporary workaround

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Mon, 13 Apr 2020 at 15:04, <maya%netbsd.org@localhost> wrote:
>
> On Mon, Apr 13, 2020 at 02:25:50PM +0100, Chavdar Ivanov wrote:
> > On Mon, 13 Apr 2020 at 03:13, <maya%netbsd.org@localhost> wrote:
> > >
> > > On Mon, Apr 13, 2020 at 12:36:35AM +0100, Mike Pumford wrote:
> > > >
> > > >
> > > > On 12/04/2020 17:14, Rhialto wrote:
> > > > > New developments :)
> > > > >
> > > > > In www/firefox/patches/patch-browser_app_profile_firefox.js I find
> > > > >
> > > > > +// Disable multiprocess window support. Workaround for PR 53273.
> > > > > +pref("browser.tabs.remote.autostart", false);
> > > > >
> > > >
> > > > >
> > > > > I still had to disable webGL to visit google maps, but that is a
> > > > > separate matter.
>
> I am wondering about people for whom, the non-success of WebGL results
> in a crash. I haven't seen this at all, and in theory it should use a
> separate process to test GL to avoid crashing the browser if something
> goes horribly wrong.
>
I am getting:
.....
Reading symbols from /usr/pkg/lib/firefox/firefox...
(No debugging symbols found in /usr/pkg/lib/firefox/firefox)
[New process 1]
[New process 75]
.....
.....
[New process 4]
[New process 3]
[New process 2]
Core was generated by `firefox'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000077ed22b85eba in _lwp_kill () from /usr/lib/libc.so.12
[Current thread is 1 (process 1)]
(gdb) bt
#0  0x000077ed22b85eba in _lwp_kill () from /usr/lib/libc.so.12
#1  0x000077ed1088ea41 in ?? () from /usr/pkg/lib/firefox/libxul.so
#2  0x000077ed110f8e67 in ?? () from /usr/pkg/lib/firefox/libxul.so
#3  0x000077ed22ab0020 in opendir () from /usr/lib/libc.so.12
#4  0x000000010000000b in ?? ()
#5  0x0000000000000000 in ?? ()

which seems pretty useless, but is consistent for all the versions I
have tested not to be working.


-- 
----