Closed
Bug 1129247
Opened 10 years ago
Closed 10 years ago
Stop using full release-mode assertions for media invariants
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: bholley, Assigned: bholley)
References
Details
Attachments
(2 files)
2.13 KB,
patch
|
Waldo
:
review+
lmandel
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
8.08 KB,
patch
|
mattwoodrow
:
review+
lmandel
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
The media code is racey, and our test coverage is poor - so CI doesn't give us a lot of confidence that our code is bug-free. As such, I've recently gotten into the habit of asserting certain invariants with release-mode assertions so that I can find bugs in the wild. This has worked quite well, but isn't a good long-term strategy - for most of these bugs, we'd still rather just be buggy than crash for release builds. This strategy only makes sense as a diagnostic on branches where we can rapidly deploy fixes (i.e. Nightly and Aurora).
I'm going to add some infrastructure that lets us do that.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8558868 -
Flags: review?(jwalden+bmo)
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8558870 -
Flags: review?(matt.woodrow)
Comment 3•10 years ago
|
||
Comment on attachment 8558868 [details] [diff] [review]
Part 1 - Introduce MOZ_DIAGNOSTIC_ASSERT. v1
Review of attachment 8558868 [details] [diff] [review]:
-----------------------------------------------------------------
::: mfbt/Assertions.h
@@ +387,5 @@
>
> +#ifdef RELEASE_BUILD
> +# define MOZ_DIAGNOSTIC_ASSERT(...) MOZ_ASSERT(__VA_ARGS__)
> +#else
> +# define MOZ_DIAGNOSTIC_ASSERT(...) MOZ_RELEASE_ASSERT(__VA_ARGS__)
It's probably better to have these as
# define MOZ_DIAGNOSTIC_ASSERT MOZ_ASSERT
# define MOZ_DIAGNOSTIC_ASSERT MOZ_RELEASE_ASSERT
so that we can worry less about possibly triggering MSVC's variadic macro bugs.
Attachment #8558868 -
Flags: review?(jwalden+bmo) → review+
Updated•10 years ago
|
Attachment #8558870 -
Flags: review?(matt.woodrow) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Assignee | ||
Comment 5•10 years ago
|
||
Comment on attachment 8558870 [details] [diff] [review]
Part 2 - Use MOZ_DIAGNOSTIC_ASSERT instead of MOZ_RELEASE_ASSERT in media code. v1
Approval request for both patchesaurora - we've got several of these assertions that we have fatal on all builds, and we want to make them non-fatal for beta and release. ~Zero risk.
Attachment #8558870 -
Flags: approval-mozilla-aurora?
Comment 6•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/b5fee3301951
https://hg.mozilla.org/mozilla-central/rev/8c84373abd46
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Comment 7•10 years ago
|
||
Comment on attachment 8558868 [details] [diff] [review]
Part 1 - Introduce MOZ_DIAGNOSTIC_ASSERT. v1
I agree with comment 5. These changes are also trivial. Aurora+
Attachment #8558868 -
Flags: approval-mozilla-aurora+
Updated•10 years ago
|
Attachment #8558870 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Updated•10 years ago
|
status-firefox37:
--- → affected
Comment 8•10 years ago
|
||
NB part two doesn't apply cleanly to aurora. I'm going through the backlog of changes which weren't critical for beta and preparing uplift requests.
Comment 9•10 years ago
|
||
Landed on 37 with some conflicts resolved manually.
https://hg.mozilla.org/releases/mozilla-aurora/rev/f2b73f65dad9
https://hg.mozilla.org/releases/mozilla-aurora/rev/a4dbe6aaec36
You need to log in
before you can comment on or make changes to this bug.
Description
•