wayland_buffer_fuzzer: fix CHECK failure: U_SUCCESS(status) in
.. number_formatting.cc It was required to initialize ICU with InitializeICUForTesting to fix that as WaylandBufferManagerHost may call base::FormatNumber in certain conditions that requires ICU initialized. Also, remove call expectation for zwp_linux_dmabuf_v1.CreateParams as it's not guaranteed that it will be called (if parameters are invalid, zwp_linux_dmabuf_v1 is never called). Last but not least, always check if the terminate gpu callback is fired. If it is fired, set a callback again and continue running current fuzz test case to verify that WaylandBufferManagerHost doesn't crash even after it has already fired one terminate gpu callback that a potential client just ignored. Bug: 1164654 Change-Id: Ia3f0c248a1e9587a63d9d4cc230defc39357e8f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2624210Reviewed-by:Nick Yamane <nickdiego@igalia.com> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#842914}
Showing
Please register or sign in to comment