New issue
Advanced search Search tips

Issue 786360 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Sanitizer CHECK failure in ((data_.proc_self_maps.len)) > ((0)) (0, 0)

Project Member Reported by ClusterFuzz, Nov 17 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5776993894531072

Fuzzer: inferno_flicker
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  ((data_.proc_self_maps.len)) > ((0)) (0, 0)
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=513689:513705

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5776993894531072

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: kkaluri@chromium.org
Components: Blink
Labels: M-64 Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

Comment 2 by junov@chromium.org, Nov 20 2017

Components: -Blink Internals>Media>Video
The info in the clusterfuzz report is pretty useless, but the minimized test case has nothing but an HTML video element in it. Assuming it has to do with the decoder choking on a bad or special case mp4 file.
Cc: mmoroz@chromium.org infe...@chromium.org
Bad stack from CF?
Status: WontFix (was: Untriaged)
Bad OOM stack.

[1:6:1117/004535.631073:FATAL:memory_linux.cc(35)] Out of memory.
Project Member

Comment 5 by ClusterFuzz, Nov 27 2017

Labels: ClusterFuzz-Top-Crash ReleaseBlock-Beta
Testcase 5776993894531072 is a top crash on ClusterFuzz for linux platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 6 by ClusterFuzz, Nov 27 2017

Labels: Needs-Feedback
ClusterFuzz testcase 5776993894531072 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

Sign in to add a comment