Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: yosin
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/e3d2a5b25ef09f4c8458db05080e604efae9c1aa
Time: Fri Oct 28 07:19:30 2016
Lines 300 of file CompositeEditCommand.cpp which potentially caused crash are changed in this cl (frame #6, "blink::CompositeEditCommand::applyCommandToComposite"). 

Files ApplyStyleCommand.cpp, InsertTextCommand.cpp are changed in this cl (and is part of stack frame #2, "blink::ApplyStyleCommand::applyRelativeFontStyleChange"; frame #3, "blink::ApplyStyleCommand::doApply")
Minimum distance from crash line to modified line: 0. (file: CompositeEditCommand.cpp, crashed on: 300, modified: 300).

@yosin -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Lower to Pri-2, since real world usage of ApplyStyle command is low.

ClusterFuzz has detected this issue as fixed in range 452175:452490.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5895503083732992

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  getFlag
  isTextNode
  blink::ApplyStyleCommand::applyRelativeFontStyleChange
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=428077:428348
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=452175:452490

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97XCtg_ZegQBMpu8BG7BMqEuqLTGYZQzrdvihN7B12z3TWcoJn-8_LtMeezVMe_6I63lxbDBC8tGXBm-A7X-cs4F-hwYU5QF1T-aI3TiJ1ZHQSL6gY0RP4fA7QkfG-X9h0GxPUCM8vx6HngWxYe4InnuSGH5g?testcase_id=5895503083732992


Additional requirements: Requires Gestures

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5895503083732992 is verified as fixed, so closing issue.

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