Abrt in blink::BlobBytesProvider::AppendData |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5846005430616064 Fuzzer: inferno_layout_test_unmodified Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Abrt Crash Address: 0x03e900003372 Crash State: blink::BlobBytesProvider::AppendData blink::BlobData::AppendDataInternal blink::BlobData::AppendBytes Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=530275:530282 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5846005430616064 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Feb 24 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/db1b4e28db01ef1f2fa9f138a426165f636f07cc (Eliminate blink::BlobDataItem.). 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.
,
Feb 24 2018
This just seems to be a OOM. Although I would have expected the before-code to OOM just as much...
,
Feb 26 2018
And I can't even reproduce this... both before and after my suspected change I get the expected Uncaught RangeError: Array buffer allocation failed instead of whatever clusterfuzz was getting here...
,
Feb 26 2018
And I can reproduce the described behavior with the configuration clusterfuzz was using here, but (as I expected) there's no difference in behavior before/after the suspected regression changelist. Either way this seems like a won't fix. Creating a blob from data in memory that is too big to fit in memory causes OOM seems like everything is working as intended.
,
Mar 5 2018
ClusterFuzz testcase 5846005430616064 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Jun 15 2018
,
Jun 15 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Feb 24 2018Labels: Test-Predator-Auto-Components