Re: Firefox segfaults on NetBSD part #53 (now with reproduction steps)
On Mon 07 Nov 2016 at 07:02:58 +, co...@sdf.org wrote: > On Mon, Nov 07, 2016 at 06:51:58AM +, co...@sdf.org wrote: > > I can reproduce this behaviour fairly reliably now: kill firefox, > > restart dbus. start firefox again, try to load anything. > > > > Now I'm sad because I've been trying this repeatedly to confirm it > really is reproducible and firefox just works :-) What just seemed to work repeatably (but I'm not going to try it a 3rd time right now) is the following. I have an extension TGH (Tab Groups Helper). It can export a file with all current tabs in all groups. If you choose that menu option, it opens a window with 2 buttons, one for export, one for import. When closing that window (from the window manager, since it has no internal close button), Firefox crashes for me. Although the second time it didn't produce the messages I reported earlier. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X \X/ rhialto/at/xs4all.nl-- are condemned to reinvent it. Poorly. signature.asc Description: PGP signature
Re: Firefox segfaults on NetBSD part #53 (now with reproduction steps)
On Mon, Nov 07, 2016 at 06:51:58AM +, co...@sdf.org wrote: > I can reproduce this behaviour fairly reliably now: kill firefox, > restart dbus. start firefox again, try to load anything. > Now I'm sad because I've been trying this repeatedly to confirm it really is reproducible and firefox just works :-)
Firefox segfaults on NetBSD part #53 (now with reproduction steps)
It really may be a dbus issue. I've noticed that when I first start my machine, firefox will be in a loop where opening a link will cause the tab to crash. I can reproduce this behaviour fairly reliably now: kill firefox, restart dbus. start firefox again, try to load anything. opening from terminal it says whenever I try to load a new tab and it crashes: ###!!! [Parent][MessageChannel] Error: (msgtype=0x2C007A,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv too much recursion I seem to recall seeing these messages on fifrefox crashes on previous versions, so maybe they've changed this code path not to segfault now. Some stuff to keep in mind: - your typical netbsd user's only program using dbus is firefox. - as usual, netbsd isn't a tier one platform for dbus, and I think we might be using 'weird code' - linux typically uses epoll, so whenever there's code that has both, we're "exercising a less tested code path" .. and netbsd's poll violates POSIX (knowingly).
