-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REPORT_TIMEOUTS and REPORT_OOMS are not described in OSS Fuzz documentation #11723
Comments
ligurio
added a commit
to ligurio/lua-c-api-tests
that referenced
this issue
May 27, 2024
luaL_loadbuffer_proto_test constantly reports OOM's. These fails are false-positives and really annoying. An example of such fail is below. ==98== ERROR: libFuzzer: out-of-memory (used: 3524Mb; limit: 2560Mb) To change the out-of-memory limit use -rss_limit_mb=<N> Live Heap Allocations: 4748197972 bytes in 42448 chunks; quarantined: 8388640 bytes in 2 chunks; 103000 other chunks; total chunks: 145450; showing top 95% (at most 8 unique contexts) 2521827184 byte(s) (53%) in 25 allocation(s) #0 0x564a0a9b08c5 in realloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3 #1 0x564a0ab9cd4f in lj_mem_realloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_gc.c:873:7 #2 0x564a0ab063d3 in lj_str_alloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_str.c:287:14 #3 0x564a0abacf26 in lj_buf_str /src/lua-c-api-tests/build/luajit-v2.1/source/src/./lj_buf.h:195:10 #4 0x564a0abacf26 in lj_meta_cat /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_meta.c:304:23 #5 0x564a0ab91e54 in lj_BC_CAT /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_vm.S:428 DEDUP_TOKEN: __interceptor_realloc--lj_mem_realloc--lj_str_alloc 2147483648 byte(s) (45%) in 1 allocation(s) #0 0x564a0a9b08c5 in realloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3 #1 0x564a0ab9cd4f in lj_mem_realloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_gc.c:873:7 #2 0x564a0aba01b5 in buf_grow /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_buf.c:34:17 #3 0x564a0aba0711 in lj_buf_more2 /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_buf.c:85:5 #4 0x564a0abad075 in lj_buf_more /src/lua-c-api-tests/build/luajit-v2.1/source/src/./lj_buf.h:109:12 #5 0x564a0abad075 in lj_meta_cat /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_meta.c:289:7 #6 0x564a0ab91e54 in lj_BC_CAT /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_vm.S:428 DEDUP_TOKEN: __interceptor_realloc--lj_mem_realloc--buf_grow Fixes #85 Related to google/oss-fuzz#11723
ligurio
added a commit
to ligurio/lua-c-api-tests
that referenced
this issue
May 27, 2024
luaL_loadbuffer_proto_test constantly reports OOM's. These fails are false-positives and really annoying. An example of such fail is below. ==98== ERROR: libFuzzer: out-of-memory (used: 3524Mb; limit: 2560Mb) To change the out-of-memory limit use -rss_limit_mb=<N> Live Heap Allocations: 4748197972 bytes in 42448 chunks; quarantined: 8388640 bytes in 2 chunks; 103000 other chunks; total chunks: 145450; showing top 95% (at most 8 unique contexts) 2521827184 byte(s) (53%) in 25 allocation(s) #0 0x564a0a9b08c5 in realloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3 #1 0x564a0ab9cd4f in lj_mem_realloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_gc.c:873:7 #2 0x564a0ab063d3 in lj_str_alloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_str.c:287:14 #3 0x564a0abacf26 in lj_buf_str /src/lua-c-api-tests/build/luajit-v2.1/source/src/./lj_buf.h:195:10 #4 0x564a0abacf26 in lj_meta_cat /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_meta.c:304:23 #5 0x564a0ab91e54 in lj_BC_CAT /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_vm.S:428 DEDUP_TOKEN: __interceptor_realloc--lj_mem_realloc--lj_str_alloc 2147483648 byte(s) (45%) in 1 allocation(s) #0 0x564a0a9b08c5 in realloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3 #1 0x564a0ab9cd4f in lj_mem_realloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_gc.c:873:7 #2 0x564a0aba01b5 in buf_grow /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_buf.c:34:17 #3 0x564a0aba0711 in lj_buf_more2 /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_buf.c:85:5 #4 0x564a0abad075 in lj_buf_more /src/lua-c-api-tests/build/luajit-v2.1/source/src/./lj_buf.h:109:12 #5 0x564a0abad075 in lj_meta_cat /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_meta.c:289:7 #6 0x564a0ab91e54 in lj_BC_CAT /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_vm.S:428 DEDUP_TOKEN: __interceptor_realloc--lj_mem_realloc--buf_grow Fixes #85 Related to google/oss-fuzz#11723
ligurio
added a commit
to ligurio/lua-c-api-tests
that referenced
this issue
May 27, 2024
luaL_loadbuffer_proto_test constantly reports OOM's. These fails are false-positives and really annoying. An example of such fail is below. ``` ==98== ERROR: libFuzzer: out-of-memory (used: 3524Mb; limit: 2560Mb) To change the out-of-memory limit use -rss_limit_mb=<N> Live Heap Allocations: 4748197972 bytes in 42448 chunks; quarantined: 8388640 bytes in 2 chunks; 103000 other chunks; total chunks: 145450; showing top 95% (at most 8 unique contexts) 2521827184 byte(s) (53%) in 25 allocation(s) #0 0x564a0a9b08c5 in realloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3 #1 0x564a0ab9cd4f in lj_mem_realloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_gc.c:873:7 #2 0x564a0ab063d3 in lj_str_alloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_str.c:287:14 #3 0x564a0abacf26 in lj_buf_str /src/lua-c-api-tests/build/luajit-v2.1/source/src/./lj_buf.h:195:10 #4 0x564a0abacf26 in lj_meta_cat /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_meta.c:304:23 #5 0x564a0ab91e54 in lj_BC_CAT /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_vm.S:428 DEDUP_TOKEN: __interceptor_realloc--lj_mem_realloc--lj_str_alloc 2147483648 byte(s) (45%) in 1 allocation(s) #0 0x564a0a9b08c5 in realloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3 #1 0x564a0ab9cd4f in lj_mem_realloc /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_gc.c:873:7 #2 0x564a0aba01b5 in buf_grow /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_buf.c:34:17 #3 0x564a0aba0711 in lj_buf_more2 /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_buf.c:85:5 #4 0x564a0abad075 in lj_buf_more /src/lua-c-api-tests/build/luajit-v2.1/source/src/./lj_buf.h:109:12 #5 0x564a0abad075 in lj_meta_cat /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_meta.c:289:7 #6 0x564a0ab91e54 in lj_BC_CAT /src/lua-c-api-tests/build/luajit-v2.1/source/src/lj_vm.S:428 DEDUP_TOKEN: __interceptor_realloc--lj_mem_realloc--buf_grow ``` Fixes #85 Related to google/oss-fuzz#11723
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #3432 it was decided to provide a way for disabling reporting timeouts and OOMs, see commit 1.
But these options are not described in documentation, see 2.
Footnotes
https://github.com/google/oss-fuzz/pull/6711/commits/185f98d3863cc09506b870847aa7a503b7623b03 ↩
https://google.github.io/oss-fuzz/faq/#how-do-you-handle-timeouts-and-ooms ↩
The text was updated successfully, but these errors were encountered: