New issue
Advanced search Search tips

Issue 755001 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Indirect-leak in base::AlignedAlloc

Project Member Reported by ClusterFuzz, Aug 13 2017

Issue description

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

Fuzzer: libFuzzer_mojo_parse_message_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  base::AlignedAlloc
  mojo::edk::Channel::Message::Message
  mojo::edk::Channel::Message::Message
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=492039:492095

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: etienneb@chromium.org
Project Member

Comment 2 by ClusterFuzz, Aug 19 2017

ClusterFuzz has detected this issue as fixed in range 495780:495802.

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

Fuzzer: libFuzzer_mojo_parse_message_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  base::AlignedAlloc
  mojo::edk::Channel::Message::Message
  mojo::edk::Channel::Message::Message
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=492039:492095
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=495780:495802

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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, Aug 19 2017

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