You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have closed several bugs similar to crbug.com/389736283. The bug is about a crash on NOTREACHED() with an invalid input which should never happen in the real world except that the input is artificially created and served to the deserializer in an artificial way. When that happens, it's not safe to recover and continue, so crashing is the right choice. I have added the bug to the Clusterfuzz-Ignore hotlist, but the hotlist seems to only apply to the particular test case, not for all crashes on that NOTREACHED(). It will be great if we have a way to let Clusterfuzz know that a crash on a particular line is intentional and not file bugs.
The text was updated successfully, but these errors were encountered:
I have closed several bugs similar to crbug.com/389736283. The bug is about a crash on NOTREACHED() with an invalid input which should never happen in the real world except that the input is artificially created and served to the deserializer in an artificial way. When that happens, it's not safe to recover and continue, so crashing is the right choice. I have added the bug to the
Clusterfuzz-Ignorehotlist, but the hotlist seems to only apply to the particular test case, not for all crashes on that NOTREACHED(). It will be great if we have a way to let Clusterfuzz know that a crash on a particular line is intentional and not file bugs.The text was updated successfully, but these errors were encountered: