Crash in extensions::ShowSettingsApiBubble |
||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5014052963352576 Fuzzer: inferno_layout_test_unmodified Job Type: windows_syzyasan_chrome Platform Id: windows Crash Type: UNKNOWN Crash Address: 0x00000077 Crash State: extensions::ShowSettingsApiBubble ChromeOmniboxEditController::OnAutocompleteAccept OmniboxEditModel::OpenMatch Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_chrome&range=407477:407480 Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96D51FKaPDSnUikLHKdLyAnbj06zYjAHEIhcVAHEQPZouUACUT82YUPg9yZ2Y3S1jQBbMiNQUlLAk_0ZW6zJu14H4M_63WP7mODfbgVkiS8Hn2o8n9ascTcjUDpmhLa5cCugRLnaTk61m9BKcetN1outf5oxA?testcase_id=5014052963352576 Additional requirements: Requires Gestures Filer: rnimmagadda See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jul 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8996565733bc75e7a029e8b8d4612e2b013e63d2 commit 8996565733bc75e7a029e8b8d4612e2b013e63d2 Author: rdevlin.cronin <rdevlin.cronin@chromium.org> Date: Thu Jul 28 15:44:36 2016 [Extensions UI] Check for a browser not being found chrome::FindBrowserWithWebContents() can return null in some cases. Guard against it in showing the warning bubble. BUG= 631362 Review-Url: https://codereview.chromium.org/2191713003 Cr-Commit-Position: refs/heads/master@{#408403} [modify] https://crrev.com/8996565733bc75e7a029e8b8d4612e2b013e63d2/chrome/browser/ui/extensions/settings_api_bubble_helpers.cc
,
Jul 28 2016
I think this should be fixed by #2. meacer@, do you know if there's a way to have clusterfuzz rerun the test case? Since this particular one involves a bunch of gestures, it's hard to repro locally.
,
Jul 28 2016
I think the "Redo" button at the top does that. I clicked it and it seems to be updating with a "Pending" message.
,
Jul 28 2016
I noticed that, but wasn't sure of the value to pick. I'm assuming maybe "fixed" checks if it's fixed? (I wanted to be sure to not accidentally force it to mark as fixed.)
,
Jul 28 2016
I clicked all of them, but not sure either :) +Marty for the clusterfuzz question
,
Jul 28 2016
If you checked the "Fixed" box under redo it would re-run fixed testing. CF also seems to be having trouble reproducing this, probably because of gesture timing.
,
Aug 1 2016
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by rnimmagadda@chromium.org
, Jul 26 2016Components: Platform>Extensions Tools>Test>FindIt>CorrectResult
Labels: M-54 Findit-for-crash Te-Logged
Owner: rdevlin....@chromium.org
Status: Assigned (was: Untriaged)