mirror of https://github.com/google/oss-fuzz.git
![]() If mupdf throws an exception (extremely likely in when fuzzing), none of the resources such as the rendered pixmap, document or stream were reclaimed before exiting causing memory leaks. These leaks were blamed on the software itself, when it actually was the fuzzer implementation that leaked. Fix this by always cleaning up all resources. |
||
---|---|---|
.. | ||
Dockerfile | ||
build.sh | ||
pdf_fuzzer.cc | ||
pdf_fuzzer.options | ||
project.yaml |