AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x7fdf2cc72b38 bp 0x7fff1ba9e100 sp 0x7fff1ba9d6c0 T0) in netwerk/test/browser/browser_child_resource.js

RESOLVED DUPLICATE of bug 1385356

Status

()

RESOLVED DUPLICATE of bug 1385356
a year ago
a year ago

People

(Reporter: ahal, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a year ago
https://treeherder.mozilla.org/logviewer.html#?job_id=118977675&repo=try&lineNumber=3596

We recently discovered ASAN errors weren't turning tasks orange. Upon fixing that, this is one of two permafails. We'll need to either fix or disable this before landing a patch in bug 1385311.
(Reporter)

Updated

a year ago
See Also: → bug 1385356
Summary: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x7fdf2cc72b38 bp 0x7fff1ba9e100 sp 0x7fff1ba9d6c0 T0) in netwerk/test/browser/browser_child_resources.js → AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x7fdf2cc72b38 bp 0x7fff1ba9e100 sp 0x7fff1ba9d6c0 T0) in netwerk/test/browser/browser_child_resource.js
await BrowserTestUtils.crashBrowser(browser);

Maybe this should also be disabled if there is no crash reporter? That isn't quite accurate but otherwise we'd have to teach the harness about when these crashes are okay, for ASan.
(Reporter)

Comment 2

a year ago
Mconley came to the same conclusion in bug 1385356. I'll dupe that to this so I can put both changes up in the same review.
(Reporter)

Updated

a year ago
Duplicate of this bug: 1385356
(Reporter)

Updated

a year ago
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1385356
You need to log in before you can comment on or make changes to this bug.