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

Issue 823110 link

Starred by 1 user
Status: Verified
Owner: ----
Closed: Apr 2018
Cc:
xiaoche...@chromium.org
█ brajkumar@chromium.org
editing-dev@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

CHECK failure: false in TextIteratorTextNodeHandler.cpp

Project Member Reported by ClusterFuzz, Mar 18 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6603130083737600

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in TextIteratorTextNodeHandler.cpp
  blink::TextIteratorTextNodeHandler::HandlePreFormattedTextNode
  blink::TextIteratorTextNodeHandler::HandleTextNodeInRange
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=529050:529051

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 18 2018

Components: Blink>Editing
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.
Project Member

Comment 2 by ClusterFuzz, Mar 18 2018

Labels: Test-Predator-Auto-Owner
Owner: lukasza@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ffb5de3934abd4e16399b2f79e7100823c6076fd (Don't propagate cmdline flags that are not read by renderer processes.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 3 by lukasza@chromium.org, Mar 19 2018

Labels: Test-Predator-Wrong-CLs
Owner: yosin@chromium.org
yosin@, could you PTAL and help triage as one of third_party/WebKit/Source/core/editing/OWNERS?

I am adding Test-Predator-Wrong-CLs label and removing myself as an owner, because I think the explanation from  https://crbug.com/823148#c3  applies here as well.

Comment 4 by yosin@chromium.org, Mar 20 2018

Labels: Pri-3
Owner: ----
Status: Available (was: Assigned)

Comment 5 by xiaoche...@chromium.org, Mar 28 2018

Cc: brajkumar@chromium.org xiaoche...@chromium.org
 Issue 826388  has been merged into this issue.
Project Member

Comment 6 by ClusterFuzz, Apr 8 2018

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

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

Comment 7 by ClusterFuzz, Apr 15 2018

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

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
►

Sign in to add a comment