Closed
Bug 1477212
Opened 6 years ago
Closed 6 years ago
about:support is empty in ASAN Nightly.
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox63 | --- | affected |
People
(Reporter: gcp, Unassigned)
References
(Blocks 1 open bug)
Details
ASAN Nightly of 2018-07-19
about:support has the first large box with general config filled, but every other detail is completely empty. Copy pasting the raw output gives a ton of data, of which this looks like it might be relevant:
"crashes": "Troubleshoot data provider failed: crashes\n[Exception... \"File error: Not found\" nsresult: \"0x80520012 (NS_ERROR_FILE_NOT_FOUND)\" location: \"JS frame :: resource://gre/modules/Troubleshoot.jsm :: crashes :: line 646\" data: no]",
"sandbox": "Troubleshoot data provider failed: sandbox\nTypeError: Cc['@mozilla.org/sandbox/syscall-reporter;1'] is undefined",
Reporter | ||
Comment 1•6 years ago
|
||
This does not happen in an empty profile.
Blocks: asan-nightly-project
Reporter | ||
Comment 2•6 years ago
|
||
[Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsICrashReporter.annotateCrashReport]" nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame :: chrome://browser/content/browser.js :: onLocationChange :: line 4843" data: no] 2
onLocationChange chrome://browser/content/browser.js:4843:9
callListeners chrome://browser/content/tabbrowser.js:721:18
_callProgressListeners chrome://browser/content/tabbrowser.js:734:7
_callProgressListeners chrome://browser/content/tabbrowser.js:4472:12
onLocationChange chrome://browser/content/tabbrowser.js:4835:7
Troubleshoot data provider failed: crashes
[Exception... "File error: Not found" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: resource://gre/modules/Troubleshoot.jsm :: crashes :: line 646" data: no] Troubleshoot.jsm:148
Troubleshoot data provider failed: sandbox
TypeError: Cc['@mozilla.org/sandbox/syscall-reporter;1'] is undefined Troubleshoot.jsm:148
TypeError: $(...) is null[Learn More] aboutSupport.js:133:7
Reporter | ||
Comment 3•6 years ago
|
||
about:crashes gives
Hmm. That address doesn’t look right.
Please check that the URL is correct and try again.
Comment 4•6 years ago
|
||
(In reply to Gian-Carlo Pascutto [:gcp] from comment #0)
> ASAN Nightly of 2018-07-19
>
> about:support has the first large box with general config filled, but every
> other detail is completely empty. Copy pasting the raw output gives a ton of
> data, of which this looks like it might be relevant:
>
> "crashes": "Troubleshoot data provider failed: crashes\n[Exception...
> \"File error: Not found\" nsresult: \"0x80520012
> (NS_ERROR_FILE_NOT_FOUND)\" location: \"JS frame ::
> resource://gre/modules/Troubleshoot.jsm :: crashes :: line 646\" data: no]",
Do you have parts of crashreporting disabled in some way? The first error looks like this line:
https://dxr.mozilla.org/mozilla-central/rev/085cdfb90903d4985f0de1dc7786522d9fb45596/toolkit/modules/Troubleshoot.jsm#646
which is
let CrashReports = ChromeUtils.import("resource://gre/modules/CrashReports.jsm").CrashReports;
but it's correctly inside an AppConstants.MOZ_CRASHREPORTER check...
> "sandbox": "Troubleshoot data provider failed: sandbox\nTypeError:
> Cc['@mozilla.org/sandbox/syscall-reporter;1'] is undefined",
This seems to be because the sandbox syscall reporter is missing. I don't know why that'd be but you've reviewed some of that code so you probably have a better idea than me...
I'm a bit surprised generally because I think we tried to make about:support not be so brittle even if one of the data reporters failed, and the errors bear that out but you're saying the entire thing is still empty? Nothing shows up at all?
Flags: needinfo?(gpascutto)
Comment 5•6 years ago
|
||
(In reply to Gian-Carlo Pascutto [:gcp] from comment #2)
> TypeError: $(...) is null[Learn More] aboutSupport.js:133:7
This is probably why the page is empty... this is well weird, because it's looking for #crashes-title, which is here:
https://searchfox.org/mozilla-central/source/toolkit/content/aboutSupport.xhtml#292
which is also behind a MOZ_CRASHREPORTER check. Presumably I'm missing something, because at a glance this looks like some kind of frankenbuild where some parts think the crashreporter exists and other parts don't.
Comment 6•6 years ago
|
||
(In reply to :Gijs (he/him) from comment #5)
> (In reply to Gian-Carlo Pascutto [:gcp] from comment #2)
> > TypeError: $(...) is null[Learn More] aboutSupport.js:133:7
>
> This is probably why the page is empty... this is well weird, because it's
> looking for #crashes-title, which is here:
>
> https://searchfox.org/mozilla-central/source/toolkit/content/aboutSupport.
> xhtml#292
>
> which is also behind a MOZ_CRASHREPORTER check. Presumably I'm missing
> something, because at a glance this looks like some kind of frankenbuild
> where some parts think the crashreporter exists and other parts don't.
(the access for that being here: https://searchfox.org/mozilla-central/source/toolkit/content/aboutSupport.js#127-134 , also behind a MOZ_CRASHREPORTER check)
If you put `AppConstants.MOZ_CRASHREPORTER` in the browser console, what comes out?
Reporter | ||
Comment 8•6 years ago
|
||
I unpacked this over the regular Nightly install. I don't know if that is an issue or not, because an empty profile works.
about:buildconfig
Built from https://hg.mozilla.org/mozilla-central/rev/690cb3015db6645b335ac4835a50073cb6a3e23c
/builds/worker/workspace/build/src/clang/bin/clang -fgnu89-inline -B /builds/worker/workspace/build/src/gcc/bin -std=gnu99 6.0.0 -Qunused-arguments -Wall -Wempty-body -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wunreachable-code-return -Wclass-varargs -Wloop-analysis -Werror=non-literal-null-conversion -Wstring-conversion -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wformat -Wformat-security -Wno-gnu-zero-variadic-macro-arguments -fsanitize=address -U_FORTIFY_SOURCE -fno-common -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe
/builds/worker/workspace/build/src/clang/bin/clang++ -B /builds/worker/workspace/build/src/gcc/bin
MOZ_AUTOMATION=1 --enable-update-channel=nightly MOZILLA_OFFICIAL=1 '--enable-optimize=-O2 -gline-tables-only' 'CC=/builds/worker/workspace/build/src/clang/bin/clang -fgnu89-inline -B /builds/worker/workspace/build/src/gcc/bin' 'CXX=/builds/worker/workspace/build/src/clang/bin/clang++ -B /builds/worker/workspace/build/src/gcc/bin' --enable-address-sanitizer MOZ_STDCXX_COMPAT=1 --enable-valgrind --enable-js-shell --disable-profiling RUSTC=/builds/worker/workspace/build/src/rustc/bin/rustc CARGO=/builds/worker/workspace/build/src/rustc/bin/cargo RUSTDOC=/builds/worker/workspace/build/src/rustc/bin/rustdoc RUSTFMT=/builds/worker/workspace/build/src/rustc/bin/rustfmt LLVM_CONFIG=/builds/worker/workspace/build/src/clang/bin/llvm-config --enable-rust-simd --enable-address-sanitizer-reporter --disable-elf-hack MAKE=/usr/bin/make --disable-crashreporter --disable-install-strip
Downloaded from: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/firefox-63.0a1.en-US.linux-x86_64-asan-reporter.tar.bz2
Reporter | ||
Comment 9•6 years ago
|
||
This is fixed in the current build.
Reporter | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•