Timeout in net_http_server_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6184749919109120 Fuzzer: libFuzzer_net_http_server_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: net_http_server_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6184749919109120 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
,
Jan 17 2018
,
Jan 19 2018
,
Jan 29 2018
Majority of time is being spent in net::HttpServer::ParseHeaders.
- 98.83% 3.76% net_http_server net_http_server_fuzzer [.] net::HttpServer::ParseHeaders
- 95.07% net::HttpServer::ParseHeaders
+ 31.99% std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::append
+ 23.07% base::TrimWhitespaceASCII
+ 17.52% base::ToLowerASCII
+ 9.77% std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::reserve
+ 3.77% std::__1::__tree<std::__1::__value_type<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::_
+ 3.54% net::(anonymous namespace)::charToInput
1.88% __sanitizer_cov_trace_pc_guard
+ 1.37% std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::append
+ 3.76% 0xf23e258d4c544155
,
Feb 28 2018
,
Mar 1 2018
Well, this seems to reparse headers every time, until it gets a full HTTP message?
,
Apr 17 2018
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by brajkumar@chromium.org
, Jan 17 2018Components: Internals>Network
Labels: Test-Predator-Wrong CF-NeedsTriage