New issue
Advanced search Search tips

Issue 713185 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in base::FilePath::Append

Project Member Reported by ClusterFuzz, Apr 19 2017

Issue description

Labels: Test-Predator-Wrong M-58
Owner: jiameng@chromium.org
Status: Assigned (was: Untriaged)
The result is a list of CLs that change the crashed files. 

Author: jiameng
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/d518643748bffd4d67c504a5181489ab75b89a1d
Time: Wed Feb 08 01:48:22 2017
Lines 335 of file blink_test_runner.cc which potentially caused crash are changed in this cl (frame #4, "content_shell!content::BlinkTestRunner::GetAbsoluteWebStringFromUTF8Path+0x6b").
Minimum distance from crash line to modified line: 0. (file: blink_test_runner.cc, crashed on: 335, modified: 335).
Hello,
Would you please give me more detail so that I could reproduce the error from my side?
Thanks
Project Member

Comment 3 by ClusterFuzz, Apr 20 2017

ClusterFuzz has detected this issue as fixed in range 465765:465806.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000017
Crash State:
  base::FilePath::Append
  content::BlinkTestRunner::GetAbsoluteWebStringFromUTF8Path
  test_runner::EventSender::BeginDragWithFiles
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=448729:448967
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=465765:465806

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94RcYi-zJucz3Fkx0D8C5hKhT86WlbiDqWvUJowFQaXoHMYEUV_lkHw_nArdeCbLwd4zEmA_rAENKDQR1SUAaM1bWyts52B_M5ZSqy-JOgQtcKjJFERNnCcT8xreATslue8_gC4xXTwaF5owuoGUp942Kf4jqQYAnVdd6cDhdINvkpobVIclkAIa7ah8yRaBg1jKpQnVRn_GaMG5UK_QwtdtvtnOPLWK9xX6-HXXRequvoU9505Bjf4sxiROw-VkG4rTRQIEZ_wuGmFBNOnMFC4gRyj7BH5brAtQywBz1uypOIed9RfJGNZmqF69D2OUeUv-FvdywjW7StzM4aFAHuIvVAjf-JCCrUbNY8gCXYciRkaI28?testcase_id=5395109760991232


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 4 by ClusterFuzz, Apr 20 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5395109760991232 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