New issue
Advanced search Search tips

Issue 912993 link

Starred by 1 user
Status: Verified
Owner:
behdad@chromium.org
Closed: Jan 4
Cc:
js...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in hb_vector_t<CFF::OpStr, 8u>::alloc

Project Member Reported by ClusterFuzz, Dec 7 
Detailed report: https://clusterfuzz.com/testcase?key=5644474732249088

Fuzzer: libFuzzer_harfbuzz_fuzzer
Fuzz target binary: harfbuzz_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  hb_vector_t<CFF::OpStr, 8u>::alloc
  hb_vector_t<CFF::OpStr, 8u>::resize
  hb_vector_t<CFF::OpStr, 8u>::push
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613962:613964

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
Project Member

Comment 1 by ClusterFuzz, Dec 7

Labels: OS-Chrome
Project Member

Comment 2 by ClusterFuzz, Dec 7

Components: Blink>Fonts
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.
Project Member

Comment 3 by ClusterFuzz, Dec 7

Cc: mmoroz@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Comment 4 by mmoroz@chromium.org, Dec 8

Cc: -mmoroz@chromium.org js...@chromium.org
Owner: behdad@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by behdad@chromium.org, Dec 8 

Let's wait a couple days.  The new roll should fix this.
Project Member

Comment 6 by ClusterFuzz, Jan 4 

ClusterFuzz has detected this issue as fixed in range 619688:619690.

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

Fuzzer: libFuzzer_harfbuzz_fuzzer
Fuzz target binary: harfbuzz_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  hb_vector_t<CFF::OpStr, 8u>::alloc
  hb_vector_t<CFF::OpStr, 8u>::resize
  hb_vector_t<CFF::OpStr, 8u>::push
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613962:613964
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=619688:619690

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 7 by ClusterFuzz, Jan 4

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