New issue
Advanced search Search tips

Issue 842119 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: p in pickle.cc

Project Member Reported by ClusterFuzz, May 11 2018

Issue description

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

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  p in pickle.cc
  base::Pickle::Resize
  base::Pickle::WriteString16
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=523878:523927

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

Additional requirements: Requires HTTP

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 11 2018

Components: Internals>Core
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.
Cc: pnangunoori@chromium.org
Labels: M-67 Test-Predator-Wrong
Owner: ossu@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “ipc_message_utils.h” assigning to concern owner from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/fdd19a3a59659ea485633fe69005ca2b8c4d7ea5

@ossu -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Comment 3 by ossu@chromium.org, May 16 2018

Any idea how long this fuzzer has been running? This looks like it's regressed recently and my CL is almost a year old.
Project Member

Comment 4 by ClusterFuzz, Jul 14

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5517227739316224 appears to be flaky, updating reproducibility label.
Project Member

Comment 5 by ClusterFuzz, Jul 14

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5517227739316224 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment