Issue metadata
Sign in to add a comment
|
parsed_output == double_parsed_output. Parser/Writer mismatch. |
||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5368468754137088 Fuzzer: libfuzzer_base_json_correctness_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: parsed_output == double_parsed_output. Parser/Writer mismatch. Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=428777:428862 Minimized Testcase (1.52 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96c-Cjl_nFVyoFRknDyE2gno9Yb1nKaequfa2P6zcYr7FluQsm0VKWQr6qb67YDcViZR7WvtkKfEzCQy2BemEM0eMDVy36hBxwRNhZSNAZ_vCJ7BTgM7TkBg7Qsfn-OvfMidF83cunzYRT4mmxty9D3CtrsEQ?testcase_id=5368468754137088 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Nov 3 2016
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 3 2016
,
Nov 4 2016
,
Nov 4 2016
This appears to flag a correctness bug, yes?
,
Nov 4 2016
Yes right.
,
Nov 7 2016
Why did we close this? Shouldn't we treat this as a functional bug?
,
Nov 7 2016
,
Feb 11 2017
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Nov 3 2016