CHECK failure: count <= MaxElementCountInBackingStore<T>() in PartitionAllocator.h |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5027677772972032 Fuzzer: inferno_twister Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: count <= MaxElementCountInBackingStore<T>() in PartitionAllocator.h QuantizedSize<blink::CSSParserToken> AllocationSize Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=469308:469332 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5027677772972032 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 22 2017
Predator and CL could not provide any possible suspects. Using Code Search for the file, "PartitionAllocator.h" assigning to the concern owner. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/0820c8882ec4691521bb7767877abc30123177d4 @keishi -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Sep 11 2017
This is probably working as intended — the caller probably asked for an impossible |count|.
,
Sep 20 2017
ClusterFuzz testcase 5027677772972032 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 |
||||
Comment 1 by tkent@chromium.org
, Aug 20 2017