New issue
Advanced search Search tips

Issue 639838 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

IsSane() in snapshot.h

Project Member Reported by ClusterFuzz, Aug 22 2016

Issue description

Components: Tools>Test>FindIt>NoResult
Labels: M-54 Needs-triage Te-Logged
Suspected CLs:
================
Findit failed to find any stack trace. Is it in a new format?

Unable to find the suspect, as there is no stack trace for the crash.

Labels: -Needs-triage
Owner: yangguo@chromium.org
Status: Assigned (was: Untriaged)
Through code search on file snapshot.h, suspected culprit CL could be
https://chromium.googlesource.com/v8/v8/+/533453f9290b5668097f8db5362407f6e73a1d18

yangguo@, could you please take a look and reassign if it is not related your changes.
Thank you
Project Member

Comment 3 by ClusterFuzz, Aug 25 2016

ClusterFuzz has detected this issue as fixed in range 413961:414068.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4675544157519872

Fuzzer: libfuzzer_v8_regexp_parser_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsSane() in snapshot.h
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=413192:413325
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=413961:414068

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv966aHk9rp38218xf1K63piIeP4yUaweeGS1NfnXT7oiH3YNOrQNz4NU4w69TFP1tyCNnjKXxAlMzwbvyzQbt1sp6belM_QcmiudUjK1itvLbG3kO4jHCIzchRuD0UVcWegyY94ZCQGW8wffC7cx4JgjpFxcEA?testcase_id=4675544157519872

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 4 by ClusterFuzz, Aug 25 2016

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Labels: ClusterFuzz-Wrong
Status: Assigned (was: Verified)
Re-Opening the issue as Clusterfuzz has detected the crash again, Clusterfuzz update in the next comment.Thank you 
Project Member

Comment 6 by ClusterFuzz, Aug 25 2016

Project Member

Comment 7 by ClusterFuzz, Aug 26 2016

ClusterFuzz has detected this issue as fixed in range 414243:414324.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6417853240836096

Fuzzer: libfuzzer_v8_wasm_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsSane() in snapshot.h
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=414117:414243
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=414243:414324

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97VnwM9wcDaGB4MqCkM9UBKES--dxC5Ips5No_PaLNAwkXMqP_UtgYeUmu6rOd5P1w5fAW-awoEGgBoV2VVaI8HXd52-nDuZBkfA6h9yg6GrZ2DcdqutrbUS29bgQgaUMF7T9QvL4eBulhjsMnlQJ3z3h6XUA?testcase_id=6417853240836096

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 8 by ClusterFuzz, Aug 26 2016

Project Member

Comment 9 by ClusterFuzz, Aug 28 2016

ClusterFuzz has detected this issue as fixed in range 414881:414933.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5447081127051264

Fuzzer: libfuzzer_v8_json_parser_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsSane() in snapshot.h
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=414647:414671
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=414881:414933

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94zfXCmX7g-vS_q89x0L6s5AlK4ExcLntebjnFvku617ferNNpJ9_wOjxXaRGEwwZK3336gR5t_TGuoGrCCg3Ykh6eXn4IKR_3WlEOkPi_ktsuKaW1Kbv3ZmWxU8Q9EihjwJh7FZutE7OpwH9tNwo4wassxhQ?testcase_id=5447081127051264

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 11 by ClusterFuzz, Sep 1 2016

ClusterFuzz has detected this issue as fixed in range 414974:414981.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4510650414137344

Fuzzer: libfuzzer_v8_regexp_parser_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsSane() in snapshot.h
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=414965:414974
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=414974:414981

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97ClXy5y6g82nzrkMgXLTZCXDgEeqpQN60W2vnhHDs3KHq7m315bfUO6s9eLi-0RDWg5J3H7fAnShFlWVVzgpsuORjhAVVbzzZeV1IkyicOyKXYIaVtpgx8uLNpqVUUhMn7Y_NfteohGetPWMbdkVWKoyXjrg?testcase_id=4510650414137344

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Components: -Tools>Test>FindIt>NoResult
Project Member

Comment 13 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Assigned)
Bulk-WontFixing these bugs. This was a bug on ClusterFuzz side, see bug 717534. We will start seeing new testcases auto-filed in a day or two. We can't leave these open as ClusterFuzz won't autoverify them after ClusterFuzz-Wrong label.
Labels: -ClusterFuzz-Wrong
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.

Sign in to add a comment