On Wednesday, 18 September 2019 08:51:54 BST Emmanuel Vasilakis wrote: > On 18/9/19 1:19 π.μ., Walter Dnes wrote: > > On Tue, Sep 17, 2019 at 06:16:22PM +0300, Emmanuel Vasilakis wrote > > > >> I've compiled firefox using these use flags: > >> > >> clang custom-cflags custom-optimization dbus gmp-autoupdate hwaccel lto > >> pgo screenshot startup-notification system-av1 system-harfbuzz > >> system-icu system-jpeg system-libevent system-libvpx system-sqlite > >> system-webp > >> > >> (Didn't really change anything from previous firefox versions I > >> compiled). > >> > > You may not have changed, but the ebuild defaults changed to use > > > > system libs, and some people have reported crashes, etc with Firefox 68. > > Try disabling the system-av1 system-harfbuzz system-icu system-jpeg > > system-libevent system-libvpx system-sqlite system-webp USE flags. This > > will force Firefox to build with its own internal versions of these > > libs. The build may take longer. > > > >> firefox-bin (69.0) behaves ok. > >> > > firefox-bin is self-contained, and uses its own internal libs... hmmm. > > Hi, thanks. > > I've always used system-% use flags for firefox, never had a problem, > but yeah things could have changed in this version.
Things have definitely changed with this version. From a previous thread on FF 68 posted in this M/L and some experimentation on my systems it seems the way addons are processed in FF 68 could cause FF to barf when being launched. The fact FF works fine when launched with --safe-mode pointed to this and (re)moving addonStartup.json.lz4 fixed the problem here. > Right now I'm compiling with disabled custom-cflags. Next will be to > disable custom-optimization and if those don't help, I'll start > disabling system-% flags. > > I've done an strace and it seems to hang waiting for a futex... So the browser is waiting for some value in memory to change or to be released from some other process before it can be used by FF ... I think. > Only problem is each try is gonna take ~5 hours on my poor machine. :-) > > We'll see! The high CPU could be indicating a graphics issue, where the browser cannot use hardware acceleration for some reason on your system and it falls back on software rendering. It may be worth running some browser rendering tests to confirm this. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
