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

Issue 812308 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Breakpoint in blink::FontCache::CrashWithFontInfo

Project Member Reported by ClusterFuzz, Feb 14 2018

Issue description

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

Fuzzer: attekett_surku_fuzzer
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0xffffdc84897fb400
Crash State:
  blink::FontCache::CrashWithFontInfo
  blink::HarfBuzzShaper::ShapeSegment
  blink::HarfBuzzShaper::Shape
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Project Member

Comment 1 by ClusterFuzz, Feb 14 2018

Components: Platform
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Cc: dcheng@chromium.org brajkumar@chromium.org
Labels: Test-Predator-Wrong
Unable to find the actual suspect through code search and observing no CL under regression range. This might be duplicate of  issue 788521 , hence cc'ing @dcheng for more updates on this issue.

Thanks!
Labels: CF-NeedsTriage
Project Member

Comment 4 by ClusterFuzz, Jul 19

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 5085158936674304 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment