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

Issue 712979 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in blink::LocalFrame::setDOMWindow

Project Member Reported by ClusterFuzz, Apr 19 2017

Issue description

Cc: msrchandra@chromium.org
Components: Blink>Loader
Labels: M-60 Test-Predator-Correct-CLs
Owner: japhet@chromium.org
Status: Assigned (was: Untriaged)
Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: japhet
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/ace017f26fd8cb8d123238e41c2f0e11f5daacd6
Time: Tue Mar 21 21:17:38 2017
Lines 908, 943 of file DocumentLoader.cpp which potentially caused crash are changed in this cl (frame #1, "blink::DocumentLoader::installNewDocument"; frame #2, "blink::DocumentLoader::replaceDocumentWhileExecutingJavaScriptURL"). 

File FrameLoader.cpp is changed in this cl (and is part of stack frame #3, "blink::FrameLoader::replaceDocumentWhileExecutingJavaScriptURL"; frame #5, "blink::FrameLoader::prepareRequestForThisFrame"; frame #6, "blink::FrameLoader::load")
Minimum distance from crash line to modified line: 0. (file: DocumentLoader.cpp, crashed on: 905, modified: 905).

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

Comment 2 by ClusterFuzz, Apr 19 2017

ClusterFuzz has detected this issue as fixed in range 460191:460218.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x000000c4
Crash State:
  blink::LocalFrame::setDOMWindow
  blink::DocumentLoader::installNewDocument
  blink::DocumentLoader::replaceDocumentWhileExecutingJavaScriptURL
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=458506:458565
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=460191:460218

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94S-xOXYOnhxwC784buiXHc26PhR0gUw2MBDbf0d_Z8yPY2b_U9lOEbufirxUyIdaJSk030htSZ9qRTahkb4CqybnJ5kOCyx6pRe4nmbb99097c3ZnZu1Ow9YMeh70bD_jOA6gBDaRDXQ_bembdJw19aNH6FLCJebrzFtnChpCeZl_QICn81WauRw4rekkLOTY0sdRSN6X7ume7EnNJhVWJGpfhYqUKYxdYc-rhtWkecgwZYNZ6Bhf6J8SBpF_gZA7xkAosW6ViW6ZjcsQ56glQ13kHPrncXstrXg3F66JrOsB1gEHZXfgDPb2myOyNqhH0TmCjjk2RnwD-J3qIx3Y48YRDO9Zc6D4PX5qxziIiLhE1daHDNRD8L5xQA5HFugoS_8navIAKLPm_3oExMcEpwIE2mw?testcase_id=5148079818014720


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

Comment 3 by ClusterFuzz, Apr 19 2017

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

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

Sign in to add a comment