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

Issue 762420 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Out until 24 Jan
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: params.origin.IsSamePhysicalOriginWith(url::Origin(params.url)). url:http://NUM

Project Member Reported by ClusterFuzz, Sep 6 2017

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  params.origin.IsSamePhysicalOriginWith(url::Origin(params.url)).  url:http://NUM
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=406033:406232

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Labels: M-61 Test-Predator-Wrong CF-NeedsTriage
Could some one please look into the issue, as there is no error cpp or cc file in the testcase to find the possible suspect.
Thank You.
Cc: msrchandra@chromium.org och...@chromium.org pnangunoori@chromium.org
Labels: -M-61 -CF-NeedsTriage M-62
Owner: nasko@chromium.org
Status: Assigned (was: Untriaged)
As per the  Issue 700323  owner assigning this issue to @nasko.

@nasko -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.
Project Member

Comment 3 by ClusterFuzz, Sep 23 2017

Labels: OS-Windows OS-Mac

Comment 4 by nasko@chromium.org, Sep 28 2017

The GN config given in the test case actually causes compile failure:

clang: error: argument '-fsanitize-coverage=[func|bb|edge]' is deprecated, use '-fsanitize-coverage=[func|bb|edge],[trace-pc-guard|trace-pc]' instead [-Werror,-Wdeprecated]

How do I fix this so I can replicate the failure locally? I tried the repro tool, but it also failed.

Project Member

Comment 5 by ClusterFuzz, Oct 1 2017

Components: Internals>Core
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Project Member

Comment 7 by ClusterFuzz, May 16 2018

ClusterFuzz has detected this issue as fixed in range 558997:559000.

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

Fuzzer: inferno_twister
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  params->origin.IsSamePhysicalOriginWith(url::Origin(params->url)).  url:http://N
  content::RenderFrameImpl::SendDidCommitProvisionalLoad
  content::RenderFrameImpl::DidCommitProvisionalLoad
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=406033:406232
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=558997:559000

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

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 8 by ClusterFuzz, May 16 2018

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