mediasoup: LeakSanitizer fatal errors
fuzzer generates this output:
NEW_FUNC[1/90]: 0x76b050 in std::vector<RTC::RTCP::SenderReport*, std::allocator<RTC::RTCP::SenderReport*> >::begin() /usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/bits/stl_vector.h:548
NEW_FUNC[2/90]: 0x76b1e0 in std::vector<RTC::RTCP::SenderReport*, std::allocator<RTC::RTCP::SenderReport*> >::end() /usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/bits/stl_vector.h:566
==10==Could not attach to thread 7 (errno 1).
==10==Could not attach to thread 8 (errno 1).
==10==Failed suspending threads.
==7==LeakSanitizer has encountered a fatal error.
==7==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1
==7==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
MS: 1 ChangeBit-; base unit: 0761b60a503f3ef1eabd57414e819ee05af16580
artifact_prefix='/reports/'; Test unit written to /reports/crash-da39a3ee5e6b4b0d3255bfef95601890afd80709
Base64:
@fippo do you know how to interpret this error?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (16 by maintainers)
Commits related to this issue
- RTCP/FeedbackPsRemb: it seems to fix issue #246 but not 100% sure sue to #243 — committed to versatica/mediasoup by ibc 6 years ago
- fuzzer: run the Docker container with --cap-add SYS_PTRACE to make it possible to inspect memory leaks (related to #243) — committed to versatica/mediasoup by ibc 6 years ago
- RTCP/FeedbackPsRemb: it seems to fix issue #246 but not 100% sure sue to #243 — committed to lavarsicious/mediasoup by ibc 6 years ago
- fuzzer: run the Docker container with --cap-add SYS_PTRACE to make it possible to inspect memory leaks (related to #243) — committed to lavarsicious/mediasoup by ibc 6 years ago
OK, it seems that in
docker runthe following is required to enableptrace(needed by LSAN):--cap-add SYS_PTRACE.More info here.