CHECK failure: false in browser_process_impl.cc |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4972965577097216 Fuzzer: meacer_web_ext Job Type: linux_asan_chrome_mp Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: false in browser_process_impl.cc BrowserProcessImpl::OnKeepAliveStateChanged KeepAliveRegistry::OnKeepAliveStateChanged Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=488823:488842 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4972965577097216 Additional requirements: Requires Gestures Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 25 2017
This is the "Temporary instrumentation" for bug 625646.
,
Jul 26 2017
This check can be hit if something goes wrong in random places in Chrome, unrelated to the browser_process_impl changes. The report logs mention a NOTREACHED being hit: Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType) https://cs.chromium.org/chromium/src/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc?type=cs&q=desktop_window_tree_host_x11.cc:1097&sq=package:chromium&l=1097 Tom can you please have a look? (selected you seeing multiple recent changes to the file..)
,
Jul 28 2017
thestig: can we merge this into bug 625646?
,
Jul 28 2017
dgn: ^
,
Jul 30 2017
This issue is unrelated to the NOTIMPLEMENTED() in DesktopWindowTreeHostX11
,
Aug 29 2017
ClusterFuzz testcase 4972965577097216 is flaky and no longer reproduces, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by msrchandra@chromium.org
, Jul 25 2017Labels: Test-Predator-Wrong-CLs M-62
Owner: thestig@chromium.org
Status: Assigned (was: Untriaged)