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