New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 823028 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

Sanitizer CHECK failure in "((0)) != (0)" (0x0, 0x0)

Project Member Reported by ClusterFuzz, Mar 17 2018

Issue description

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

Fuzzer: inferno_flicker
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: Sanitizer CHECK failure
Crash Address: 
Crash State:
  "((0)) != (0)" (0x0, 0x0)
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=524986:524992

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: haraken@chromium.org brajkumar@chromium.org
Components: Blink
Labels: M-66 Test-Predator-Wrong
Owner: gyuyoung...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "FontFallbackList.cpp:182:37" and observed some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/7b20499fff2b1a299551ecf8ea8e9fbcf104e1a9%5E%21/third_party/WebKit/Source/platform/fonts/FontFallbackList.cpp

gyuyoung@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!
Components: -Blink Blink>Fonts
Once I will take a look this issue. But it seems like that this issue was caused by other CLs for now.

Comment 4 by e...@chromium.org, Apr 30 2018

Status: WontFix (was: Assigned)
Project Member

Comment 5 by ClusterFuzz, May 7 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6241729121091584 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