icu rebuild of firefox failure

[pjp]

This is on a build host in a chroot for a laptop.

I first did a rebuild of whatever icu wanted with firefox deselected from world (to avoid rebuilding it and nodejs at the same time).

After that, I then rebuilt nodejs using --oneshot. That went fine. To rebuild firefox, I used my normal update @world command.

This seemed notable:

[eccerr0r]

Well, assuming the fact other people were able to build the same firefox and looks like clang crashed with a stack trace, something going on with your clang. Does it crash in the same place each time if you just rerun it (save your old build for reference) - checked for hardware issues?

Is there a specific reason why you compiled icu and nodejs separately, though it shouldn't matter, they may pick up older deps that weren't absolutely necessary. Agreed it should be safe. I don't think I've had issues building nodejs with anything else at the same time, it's the qtwebengine thing that needs to run by itself...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?