# plxfuzz crash suppressions — known-live bugkeys, one per line.
#
# A bugkey here is treated as an ALREADY-FILED finding: crash-push.sh skips
# `gh issue create` for it (and does not re-commit it under crashes/), so a
# bug we already know about cannot spam Issues from 3 boxes for 15 days.
#
# Format, one per line:
#   <bugkey>
# where bugkey is either
#   sha256(target+sanitizer+normalized-top-3-frames)   (normal crash class), or
#   oom@<target>@rss=<cap>                              (the H1 OOM class)
# Blank lines and lines starting with '#' are ignored.
#
# Remove a line to let that bug re-open an Issue (e.g. after you believe it is
# fixed at a new pinned commit and want confirmation it is gone).

# H1 — tls_compressed_cert zlib-decompression bomb. A ~3 MB seed inflates past
# the 2048 MB rss cap, so libFuzzer reports it as an OOM. This is the KNOWN
# finding the campaign is meant to confirm/track, not re-discover; suppress it
# so it never floods Issues. (Box-b runs this target under -rss_limit_mb=2048.)
# Target-qualified so it cannot also swallow a genuine OOM in another same-cap
# target (e.g. data_record_open, also rss=2048 on box-b).
oom@tls_compressed_cert@rss=2048 tls_compressed_cert
