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

Issue 842669 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocked on:
issue 818283



Sign in to add a comment

CalculateHotModeCheckingRange() crashes with unusual HTML

Project Member Reported by ClusterFuzz, May 14 2018

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0xffffa68cf6301080
Crash State:
  blink::SimplifiedBackwardsTextIteratorAlgorithm<class blink::EditingAlgorithm<cl
  blink::SimplifiedBackwardsTextIteratorAlgorithm<class blink::EditingAlgorithm<cl
  blink::SimplifiedBackwardsTextIteratorAlgorithm<class blink::EditingAlgorithm<cl
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: brajkumar@chromium.org
Components: Blink>Editing
Labels: -Pri-1 M-67 Test-Predator-Wrong Pri-2
> Predator was unable to identify any culprit changelists for this test case. 

> Unable to find actual suspect through code search and also observing no CL under regression range, hence requesting someone from blink team to look in to it.

Thanks!

Labels: CF-NeedsTriage

Comment 3 by yosin@chromium.org, May 16 2018

Components: -Blink>Editing Blink>Editing>Spellcheck
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)
Summary: CalculateHotModeCheckingRange() crashes with unusual HTML (was: Breakpoint in blink::SimplifiedBackwardsTextIteratorAlgorithm<class blink::EditingAlgorithm<cl)
Lower to Pri-3 since this is caused by unusual HTML
Labels: -M-67 -CF-NeedsTriage M-71
Just wondering, do we have any latest update on this?
Blockedon: 818283
Seems to be caused by issue 818283.

Sign in to add a comment