-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
mpv: introspector killed, possibly OOM #12213
Comments
I suspect that libvips might be experiencing a similar issue, see: This problem seems to occur after commit libvips/libvips@65a1371, which added a couple more fuzzers. I was unable to reproduce this issue locally using: $ python infra/helper.py build_image libvips
$ python infra/helper.py build_fuzzers --sanitizer introspector --engine libfuzzer --architecture x86_64 libvips |
@kleisauke: your issue is during linking. With lto and especially with full lto there is a lot of memory needed. Reduce concurrent linking jobs to fix this. I see libvips uses meson, so |
@kasper93 Thanks for the hat tip, I'll try to build with FWIW, it seems that libvips' compile tests are also failing. However, since none of these tests are mandatory, the issue went unnoticed. I should probably use a similar workaround to the one described in #7583 (comment). |
Ah, indeed the linker issue with meson. I did this #12081 for mpv. EDIT: For reference here is the issue about it #12167 |
Hi,
This is mostly a question if there is something we could to to workaround this, I tried making targets smaller and exclude some files from introspect or, but it fails.
See: https://oss-fuzz-build-logs.storage.googleapis.com/log-49c8a121-941c-4911-be95-5f06c0c7bc8a.txt
It works locally, so it is likely OOM on build machine. I wonder if the introspector itself could be optimized to be less resource heavy?
Not highly important, but I figured to report it in case there are some low hanging fruits to grab :)
Thanks,
Kacper
The text was updated successfully, but these errors were encountered: