New issue
Advanced search Search tips

Issue 834631 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Aug 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in net::QuicStreamSequencerBuffer::BytesConsumed

Project Member Reported by ClusterFuzz, Apr 19 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  net::QuicStreamSequencerBuffer::BytesConsumed
  blink::WebLocalFrameImpl::LocalRoot
  blink::WebLocalFrameImpl::LocalRootFrameWidget
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=542401:542403

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 19 2018

Components: Blink>Internals Platform>DevTools
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, Apr 19 2018

Labels: Test-Predator-Auto-Owner
Owner: dcheng@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/4a96073611e1981d8572a2eadf7f8412a28ba157 ([OOPIF] Remove use of covariant return types for WebLocalFrame::FrameWidget().).

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 dcheng@chromium.org, Apr 19 2018

Components: -Platform>DevTools -Blink>Internals Internals>Sandbox>SiteIsolation

Comment 4 by dcheng@chromium.org, Apr 19 2018

It looks like the null check for web_frame in ChromeClientImpl::ScheduleAnimation is still necessary, though it's not entirely clear why.
Project Member

Comment 5 by ClusterFuzz, Aug 16

ClusterFuzz has detected this issue as fixed in range 583178:583179.

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

Fuzzer: inferno_twister
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  net::QuicStreamSequencerBuffer::BytesConsumed
  blink::WebLocalFrameImpl::LocalRoot
  blink::WebLocalFrameImpl::LocalRootFrameWidget
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=542401:542403
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=583178:583179

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

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.
Project Member

Comment 6 by ClusterFuzz, Aug 16

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

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

Sign in to add a comment