mirror of https://github.com/google/oss-fuzz.git
53c09d30f6
Update skia.diff to fix build breakage. Also, use $LIB_FUZZING_ENGINE instead of -lFuzzingEngine to start using -fsanitize=fuzzer |
||
|---|---|---|
| .. | ||
| BUILD.gn.diff | ||
| Dockerfile | ||
| README.md | ||
| api_fuzzers.options | ||
| build.sh | ||
| encoder.options | ||
| image_codec.options | ||
| image_filter_deserialize.options | ||
| image_filter_deserialize_width.options | ||
| json.dict | ||
| path_deserialize.options | ||
| project.yaml | ||
| region_deserialize.options | ||
| region_set_path.options | ||
| skia.diff | ||
| sksl.options | ||
| textblob_deserialize.options | ||
README.md
When bench testing image_filter_deserialize, it may be useful to have malloc_limit_mb = 500, and timeout = 10 to find actionable OOM culprits sooner.
When reproducing, add -malloc_limit_mb=100 -rss_limit_mb=0 after the repro_test to locate where big memory allocations are happening.
python infra/helper.py reproduce skia image_decode ~/Downloads/foo -malloc_limit_mb=100 -rss_limit_mb=0