New issue
Advanced search Search tips

Issue 881447 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Jan 9
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-12-25
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

CHECK failure: slice.num_characters in harfbuzz_shaper.cc

Project Member Reported by ClusterFuzz, Sep 6

Issue description

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

Fuzzer: libFuzzer_blink_harfbuzz_shaper_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  slice.num_characters in harfbuzz_shaper.cc
  blink::QueueCharacters
  blink::HarfBuzzShaper::ExtractShapeResults
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514696:514717

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Sep 6

Components: Platform
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 2 by ClusterFuzz, Sep 6

Labels: Test-Predator-Auto-Owner
Owner: js...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/befb16634bb440cf5442979ad262832b4cebd43e (Update ICU to version 60.1 + local patches).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Cc: drott@chromium.org js...@chromium.org
Components: -Platform Blink>Fonts Blink>Layout
Owner: ----
Status: Available (was: Assigned)
That ICU update was almost a year ago. 

Where is the crash stack trace?   


jshin@, stacktrace is available at the clusterfuzz testcase page: https://clusterfuzz.com/testcase?key=6220704671072256


==18291==ERROR: AddressSanitizer: ABRT on unknown address 0x053900004773 (pc 0x7f3b68d18428 bp 0x7ffd74fa58b0 sp 0x7ffd74fa5768 T0)
SCARINESS: 10 (signal)
    #0 0x7f3b68d18427 in gsignal /build/glibc-Cl5G7W/glibc-2.23/signal/../sysdeps/unix/sysv/linux/raise.c:54
    #1 0x7f3b68d1a029 in abort /build/glibc-Cl5G7W/glibc-2.23/stdlib/abort.c:89
    #2 0x7f3be963ee06 in base::debug::(anonymous namespace)::DebugBreak() base/debug/debugger_posix.cc:229:5
    #3 0x7f3be963eda3 in base::debug::BreakDebugger() base/debug/debugger_posix.cc:263:3
    #4 0x7f3be8c3ef76 in logging::LogMessage::~LogMessage() base/logging.cc:865:7
    #5 0x7f3bec5058a9 in blink::(anonymous namespace)::QueueCharacters(blink::RangeData*, blink::SimpleFontData const*, bool&, blink::BufferSlice const&) third_party/blink/renderer/platform/fonts/shaping/harfbuzz_shaper.cc:312:3
    #6 0x7f3bec50380c in blink::HarfBuzzShaper::ExtractShapeResults(blink::RangeData*, bool&, blink::ReshapeQueueItem const&, blink::SimpleFontData const*, UScriptCode, blink::CanvasRotationInVertical, bool, blink::ShapeResult*) const third_party/blink/renderer/platform/fonts/shaping/harfbuzz_shaper.cc:450:7
    #7 0x7f3bec5093ff in blink::HarfBuzzShaper::ShapeSegment(blink::RangeData*, blink::RunSegmenter::RunSegmenterRange const&, blink::ShapeResult*) const third_party/blink/renderer/platform/fonts/shaping/harfbuzz_shaper.cc:946:5
    #8 0x7f3bec50bec2 in blink::HarfBuzzShaper::Shape(blink::Font const*, blink::TextDirection, unsigned int, unsigned int, blink::RunSegmenter::RunSegmenterRange const*) const third_party/blink/renderer/platform/fonts/shaping/harfbuzz_shaper.cc:999:9
    #9 0x7f3bec510035 in blink::HarfBuzzShaper::Shape(blink::Font const*, blink::TextDirection) const third_party/blink/renderer/platform/fonts/shaping/harfbuzz_shaper.cc:1024:10
    #10 0xe26319 in blink::LLVMFuzzerTestOneInput(unsigned char const*, unsigned long) third_party/blink/renderer/platform/fonts/shaping/harfbuzz_shaper_fuzzer.cc:44:46
    #11 0xe26524 in LLVMFuzzerTestOneInput third_party/blink/renderer/platform/fonts/shaping/harfbuzz_shaper_fuzzer.cc:51:10
    #12 0xec47fa in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) third_party/libFuzzer/src/FuzzerLoop.cpp:570:15
    #13 0xe5a8b5 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) third_party/libFuzzer/src/FuzzerDriver.cpp:280:6
    #14 0xe6e1e0 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) third_party/libFuzzer/src/FuzzerDriver.cpp:713:9
    #15 0xf1d792 in main third_party/libFuzzer/src/FuzzerMain.cpp:20:10
    #16 0x7f3b68d0382f in __libc_start_main /build/glibc-Cl5G7W/glibc-2.23/csu/../csu/libc-start.c:291
    #17 0xd4c029 in _start (/mnt/scratch0/clusterfuzz/slave-bot/builds/chromium-browser-libfuzzer_linux-debug-asan_ae530a86793cd6b8b56ce9af9159ac101396e802/revisions/libfuzzer-linux-debug-589840/blink_harfbuzz_shaper_fuzzer+0xd4c029)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: ABRT /build/glibc-Cl5G7W/glibc-2.23/signal/../sysdeps/unix/sysv/linux/raise.c:54 in gsignal
==18291==ABORTING
Project Member

Comment 5 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6220704671072256 appears to be flaky, updating reproducibility label.
Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
Owner: drott@chromium.org
Status: Assigned (was: Available)
This only happened on ClusterFuzz on the 12 and 13th of December and has not reproduced since then. Re-running the job to see if it can still be made to reproduce, otherwise, let's close this as WontFix.

NextAction: 2018-12-25
Labels: -Pri-1 Pri-2
The NextAction date has arrived: 2018-12-25
Project Member

Comment 13 by ClusterFuzz, Jan 9

ClusterFuzz has detected this issue as fixed in range 621021:621022.

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

Fuzzer: libFuzzer_blink_harfbuzz_shaper_fuzzer
Fuzz target binary: blink_harfbuzz_shaper_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  slice.num_characters in harfbuzz_shaper.cc
  blink::QueueCharacters
  blink::HarfBuzzShaper::ExtractShapeResults
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514696:514717
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=621021:621022

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

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 14 by ClusterFuzz, Jan 9

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