RELEASE_ASSERT leads to confusing reports |
||
Issue descriptionAt the moment, we aren't generating CF reports for RELEASE_ASSERTs. This is bad because these are legitimate crashes, and they lead to confusion when we upload reports for these to CF. We also get some security bug reports from external contributors for these, when we don't actually care about them from a security standpoint. Some of the older documentation mentioned that these are security relevant, but that hasn't been true for a long time (actually, I'm pretty sure it never was). We should both add non-security signatures for these in CF and update the old documentation (mostly in comments).
,
Jan 17 2017
That's a good point. I'm not seeing any recent blink reports for security check failures on the test case list. They should be behaving in the same way. I wonder if something related to this changed in the recent blink assertion refactoring.
,
Jul 11
Bulk edit: archiving a few bugs assigned to me that no longer seem relevant. Please reopen if this is still something you'd like to see fixed and I'll re-evaluate it. |
||
►
Sign in to add a comment |
||
Comment 1 by aarya@google.com
, Jan 17 2017