LibFuzzer on Windows Reporting Many Unreproducible OOMs |
|||||
Issue descriptionThis is really the main issue with libFuzzer on Windows right now, it has found 23 unreproducible OOMs. See https://clusterfuzz.com/v2/testcases?job=windows_libfuzzer_chrome_asan&q=Out-of-memory We should also check to make sure none of these are being grouped improperly, meaning that there isn't an additional OOM being reported on Windows, since it is hard to believe some of these targets don't already have an OOM on Linux.
,
Oct 11
I checked, these OOMs are being deduped properly (ie: none of the fuzzers where an OOM is found on Windows find an OOM on other platforms)
,
Oct 11
,
Oct 11
,
Oct 12
The number of these is small enough that I don't think it should block bug reporting. In any case, unreproducible bugs are typically not reported so devs shouldn't notice.
,
Nov 14
This no longer seems concerning, the rate at which ClusterFuzz finds new unreproducible OOMs is unremarkable. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by metzman@chromium.org
, Oct 11