Closed Bug 1781043 Opened 2 years ago Closed 2 years ago

Disable some a11y diagnostic asserts in IPC fuzzing

Categories

(Core :: Disability Access APIs, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
105 Branch
Tracking Status
firefox-esr91 --- wontfix
firefox-esr102 --- wontfix
firefox103 --- wontfix
firefox104 --- wontfix
firefox105 --- fixed

People

(Reporter: decoder, Assigned: decoder)

Details

(Keywords: sec-other, Whiteboard: [adv-main105-])

Attachments

(1 file)

The a11y code has some diagnostic asserts that the IPC fuzzer trips very frequently. We should disable these asserts only when we are doing IPC fuzzing (through the FUZZING_SNAPSHOT ifdef).

(Marked s-s until we unhide all the other IPC fuzzing bugs).

Group: core-security → dom-core-security

Is there any bug open for those two asserts failing? Seems like the right path would be to actually fix those issues. Are there many more of these kinds of asserts that get tripped that would make that task untenable?

(In reply to Eitan Isaacson [:eeejay] from comment #2)

Is there any bug open for those two asserts failing? Seems like the right path would be to actually fix those issues. Are there many more of these kinds of asserts that get tripped that would make that task untenable?

From what I can tell, there is no actual issue. The asserts are simply not correct in the setting of IPC fuzzing. We are directly sending (wrong) data to parent actors, so the failures are expected (at least from what I can tell, looking at the code).

Group: dom-core-security → core-security-release
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
QA Whiteboard: [post-critsmash-triage]
Flags: qe-verify-
Whiteboard: [adv-main105-]
Group: core-security-release
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: