Created attachment 916586 [details] firefox-1.34.0.1_build.log(zstd) www-client/firefox-134 stalls on Java error: NS_ERROR_UNKNOWN_HOST for resource://… I had this with firefox-134.0 and now again on firefox-134.0.1 11:33.56 BUILDSTATUS@browser/locales END_langpack_manifest en-US 11:33.56 BUILDSTATUS@browser/locales START_zip firefox-134.0.1.en-US.langpack.xpi 11:33.56 /var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/srcdirs/firefox-134.0.1-cc3041c4c0b4/_virtualenvs/build/bin/python -m mozbuild.action.zip -C ../../dist/xpi-stage/locale-en-US -x **/*.manifest -x **/*.js -x **/*.ini /var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented/dist/linux-x86_64/xpi/firefox-134.0.1.en-US.langpack.xpi chrome localization browser manifest.json 11:33.70 BUILDSTATUS@browser/locales END_zip firefox-134.0.1.en-US.langpack.xpi 11:33.70 gmake[4]: Leaving directory '/var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented/browser/locales' 11:33.70 gmake[3]: Leaving directory '/var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented/browser/locales' 11:33.70 gmake[2]: Leaving directory '/var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented/browser/installer' 11:33.70 gmake[2]: Entering directory '/var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented/browser/installer' 11:33.70 gmake[2]: Nothing to be done for 'tools'. 11:33.70 gmake[2]: Leaving directory '/var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented/browser/installer' 11:33.70 gmake[1]: Leaving directory '/var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented/browser/installer' 11:33.70 gmake: Leaving directory '/var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/instrumented' started SP3 server on port 8000 console.warn: services.settings: Ignoring preference override of remote settings server console.warn: services.settings: Allow by setting MOZ_REMOTE_SETTINGS_DEVTOOLS=1 in the environment console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 238)) console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 238)) console.error: ({}) Crash Annotation GraphicsCriticalError: |[0][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=1.53941) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt console.error: ({}) [ERROR glean_core::metrics::ping] Invalid reason code active for ping usage-reporting jarlog: /var/tmp/portage/www-client/firefox-134.0.1/work/firefox_build/jarlog/en-US.log console.warn: services.settings: Ignoring preference override of remote settings server console.warn: services.settings: Allow by setting MOZ_REMOTE_SETTINGS_DEVTOOLS=1 in the environment console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 238)) console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 238)) console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 238)) console.error: ({}) console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 238)) [ERROR glean_core::metrics::ping] Invalid reason code active for ping usage-reporting console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.sys.mjs", 238)) console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error" ({type:"Amo", error:(new Error("reason: Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\"", "resource://gre/modules/RustSuggest.sys.mjs", 2228)), reason:"Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\""}) console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error" ({type:"Wikipedia", error:(new Error("reason: Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\"", "resource://gre/modules/RustSuggest.sys.mjs", 2228)), reason:"Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\""}) console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error" ({type:"Mdn", error:(new Error("reason: Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\"", "resource://gre/modules/RustSuggest.sys.mjs", 2228)), reason:"Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\""}) console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error" ({type:"Amp", error:(new Error("reason: Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\"", "resource://gre/modules/RustSuggest.sys.mjs", 2228)), reason:"Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\""}) console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error" ({type:"Yelp", error:(new Error("reason: Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\"", "resource://gre/modules/RustSuggest.sys.mjs", 2228)), reason:"Java error: \"Request error: NS_ERROR_UNKNOWN_HOST\""}) JavaScript error: resource:///modules/backup/BackupService.sys.mjs, line 108: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIProperties.get] — deadlock — When this happens, cancelling and re-doing emerge firefox (or emerge -avtDUu @world) sometimes gets it past this point, but the issue seems extremely strange - and I think the compilation process should actually die instead of just stalling forever. Perhaps it should be an upstream bug? Attached build log had to be zstd-compressed since gzip didn't get under the 1000kb limit and the raw log is almost 24MB.
Created attachment 916587 [details] emerge --info
(In reply to Michael Moon from comment #0) > > When this happens, cancelling and re-doing emerge firefox (or emerge -avtDUu > @world) sometimes gets it past this point, but the issue seems extremely > strange - and I think the compilation process should actually die instead of > just stalling forever. > How long have you waited? I don't remember when was the last time I saw the process hang with clang, but with gcc it might take up to 8 minutes before the build continues on its own. Sometimes it indeed hangs forever and requires re-launch of emerge. I've personally noticed the hang is more likely to happen if the system is under load while profiling happens - so if I "do nothing else" when firefox builds, I don't have these hangs pretty much ever anymore. This is the patch that we, and many other distros carry: https://src.fedoraproject.org/rpms/firefox/blob/rawhide/f/pgo.patch#_121 + // Disable watchdog for PGO train builds - writting profile information at + // exit may take time and it is better to make build hang rather than + // silently produce poorly performing binary. + crashAfterMS = INT32_MAX; I've also noticed that the "crash" during profiling doesn't stop the whole process of building firefox, just the profiling part. No idea how to fix that. So, yeah, fundamentally I agree it's better to hang than to produce non-pgo'd binaries, but you're right it's a pretty confusing experience and we especially as a source-based distro are faced with this, since users build their own browsers.
Pretty sure I left it sit for well over an hour on 134.0, and the system was otherwise idle - and I have a 9800X3D so it's no slouch. Setting the timeout to 2^31 ms ≈ 25 days seems a bit extreme. If it's a PGO thing, I might just disable PGO - I only turned it on recently and firefox seems to have astonishingly worse performance although I'm not sure if that's from PGO or some regression in v134
