firefox-115.9.0 - Assertion failure: i < NUM_TEST_EV...

lyallp

The only reason I am building chromium is because firefox is failing on my system, despite my best efforts, I cannot get it to run without crashing behind the scenes.

This includes masking the two latest versions and completely re-building my system, including kernel.

Split off of Chromium build time 36 hours?? after post 8826729. —Chiitoo
_________________
...Lyall

lyallp · Posted: Wed May 15, 2024 4:11 am Post subject:

I gave seamonkey a really quick try - no go, it does not work with the nextcloud login, possibly I didn't have some setting set, but I could not be bothered checking.
_________________
...Lyall

eccerr0r · Posted: Wed May 15, 2024 5:43 am Post subject:

firefox-bin also not working?

I haven't had a machine not run firefox properly in quite a while... or at least I don't use any websites that fail on the multiple machines...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

lyallp · Posted: Wed May 15, 2024 6:41 am Post subject:

firefox-bin works fine, damnit!

Re-building www-client/firefox-115.9.0, maybe having firefox-bin work on my profile has 'fixed' something in my profile?

I doubt this because I have tried resetting firefox and creating a new profile, rebuilding the system top to bottom, masking a couple of the later releases, on the assumption that it worked before.

I have just updated the kernel to 6.6.30, re-installed nvidia-drivers (as usual) and rebooted, so I will report back.

Obviously, I wold prefer firefox to chromium as it's 6 hours less compilation time.

I also prefer to build my own, rather than use -bin packages, don't ask me why, I just do... It's why I started with Gentoo just over 20 years ago!
_________________
...Lyall

lyallp · Posted: Wed May 15, 2024 7:34 am Post subject:

Firefox-115.9.0 does not work, at least for me....
sigh....

e8root · Tux's lil' helper Joined: 09 Feb 2024 Posts: 79

Did you try to build without hwaccel USE flag?
What are the USE flags anyways?

Mine are

lyallp · Posted: Wed May 15, 2024 9:38 am Post subject:

lyallp · Posted: Wed May 15, 2024 10:39 am Post subject:

Woot!

www-client/firefox-115.10.0 works!

There are multiple use flag changes in this build, including the removal of

debug
clang

and the addition of

system-av1

The added bonus is Firefox only takes 25 minutes to build, rather than 9 hours which Chromium takes to build!
_________________
...Lyall

Chiitoo · Posted: Wed May 15, 2024 11:06 am Post subject:

Split off of Chromium build time 36 hours?? after post 8826729. —Chiitoo

Looking at the 'Assertion failure: i < NUM_TEST_EV_ROOTS', I suspect the 'debug' USE-flag was in play indeed, but it seems the trace has no useful info:

lyallp · Posted: Wed May 15, 2024 11:13 am Post subject:

Yeah, I take that on board.

I was trying to diagnose and generate decent back traces for Firefox, after it was generating about 10-15 core dumps per day. I tried the debug flag Plus I changed the CFLAGS and LDFLAGS to generate debug information and rebuilt my entire system, in the hope of having a good stack trace. This, in turn caused compile times to get significantly worse. Then, firefox stopped working and I ended up building Chromium....A cascade of cock ups...

Curiously enough, initial problem seems to have gone away, as an almost guaranteed way of generating a failure was to have 2 videos running at the same time in different windows.

I tried this now and firefox didn't crash.

So, somewhere along the line, the original problem has gone away after weeks of trying to get firefox to even run, let alone crash.
_________________
...Lyall

Chiitoo · Posted: Wed May 15, 2024 11:20 am Post subject:

Did any of those builds actually have symbol names and such in the dumps before going for USE="debug"?

Could shed more light on what was going on, but it's indeed great that things got back into working order!
_________________
Kindest of regardses.

lyallp · Posted: Wed May 15, 2024 11:33 am Post subject:

My first point of call was to use gdb on the original dumps, very little info.

So, then, I updated /etc/portage/make.conf to have CFLAGS include -ggdb3 and exclude any -O2 or -O3

I also then updated LDFLAGS to include -g

Then, I emerge --empty-tree --newuse @system @world

I expected a minor performance penalty for this.

Core dumps still did not give a huge amount of detail. I figured I had missed something like 'strip' in the build process.

I still had no joy, then I tried the 'debug' use flag, that's when things broke.

I tried masking the latest couple of versions of Firefox, thinking it was working before, maybe it was an update, to no avail.

I lost sight of the fact that I had set the 'debug' USE flag.

I then tried to build chromium as an alternative browser, whilst I continued looking at firefox, but after 3 and a half DAYS of compilation, I gave up.

It was suggested that global debug symbols where slowing down compilation, so I reverted out the CFLAG/LDFLAG updates and did another emerge --empty-tree --newuse @system @world, which took 30 hours

A rebuild of firefox and it still failed.

All of this happened at the same time as grub changed (root= parm changed content), my automated kernel build and install script screwed my boot, and I had to figure out why my system was not booting, so, I was attempting to get my system booting again and build chromium and fix firefox... sigh...

I then updated my firefox use flags, as described, and that's when things started working, no more core files (yet). I think there has been a firefox update since this whole episode began but the update happened after I had enabled the debug USE flag, which was my catastrophe point.
_________________
...Lyall

Chiitoo · Posted: Wed May 15, 2024 12:19 pm Post subject:

Quite the adventure fer sure.