New issue
Advanced search Search tips

Issue 740495 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 740361
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in v8::internal::Deserializer::DecodeReservation

Project Member Reported by ClusterFuzz, Jul 10 2017

Issue description

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  v8::internal::Deserializer::DecodeReservation
  v8::internal::Deserializer::Deserializer<v8::internal::SnapshotData>
  v8::internal::Snapshot::Initialize
  
Sanitizer: address (ASAN)

Regressed: V8: 45366:45367

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 

Comment 1 by aarya@google.com, Jul 10 2017

Cc: ishell@chromium.org
Owner: mstarzinger@chromium.org
Status: Assigned (was: Untriaged)
Mergedinto: 740361
Status: Duplicate (was: Assigned)
Regression range is bogus, judging from the repro it looks like the same as  issue 740361 .
Project Member

Comment 3 by ClusterFuzz, Jul 26 2017

ClusterFuzz has detected this issue as fixed in range 46875:46876.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  v8::internal::Deserializer::DecodeReservation
  v8::internal::Deserializer::Deserializer<v8::internal::SnapshotData>
  v8::internal::Snapshot::Initialize
  
Sanitizer: address (ASAN)

Regressed: V8: 45366:45367
Fixed: V8: 46875:46876

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


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.

Sign in to add a comment