Issue metadata
Sign in to add a comment
|
Allocator is out of memory trying to allocate 0x93000000000 bytes in safe_browsing::dmg::HFSForkReadStream::Read |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4982897283694592 Fuzzer: libFuzzer_safe_browsing_hfs_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Allocator is out of memory trying to allocate 0x93000000000 bytes Crash Address: Crash State: safe_browsing::dmg::HFSForkReadStream::Read safe_browsing::dmg::ReadStream::ReadExact safe_browsing::dmg::HFSBTreeIterator::Init Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=550594:550718 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4982897283694592 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Apr 16 2018
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 16 2018
,
Apr 16 2018
,
Jul 25
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Apr 16 2018