As per the  Issue 765949  owner assigning this issue to @dcheng.
@dcheng -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

My CL just changed some names. +eae for routing this to the appropriate person on layout

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Duping this into 728256, since that one has a more useful stack.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d6cc8b72e6cc0d79db438da47fda28971880eb87

commit d6cc8b72e6cc0d79db438da47fda28971880eb87
Author: Emil A Eklund <eae@chromium.org>
Date: Tue Oct 03 01:00:38 2017

Add null check to LayoutSliderContainer::HasVerticalAppearance

Bug:  769681 
Change-Id: I28e9597aa2d1888f9890bb37d536b1e3b3886330
Reviewed-on: https://chromium-review.googlesource.com/692956
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#505897}
[modify] https://crrev.com/d6cc8b72e6cc0d79db438da47fda28971880eb87/third_party/WebKit/Source/core/layout/LayoutSliderContainer.cpp

ClusterFuzz has detected this issue as fixed in range 505590:505621.

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

Fuzzer: inferno_twister
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: Null-dereference
Crash Address: 0x0000000f
Crash State:
  blink::HasVerticalAppearance
  blink::LayoutSliderContainer::UpdateLayout
  blink::LayoutBlockFlow::PositionAndLayoutOnceIfNeeded
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=504793:504871
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=505590:505621

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

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

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