New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 696240 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

showing_context_menu_ != showing in render_widget_host_view_base.cc

Project Member Reported by ClusterFuzz, Feb 26 2017

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5395872981712896

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  showing_context_menu_ != showing in render_widget_host_view_base.cc
  content::RenderWidgetHostViewBase::SetShowingContextMenu
  RenderViewContextMenuBase::MenuWillShow
  
Sanitizer: address (ASAN)

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97O2EOXq0H6uyvpRQti4fWgckd0bMFuDkinlbxFGW1TfR2ARMji-9WMQoaEba03xDHth_1tT0i4v5ihr7o_p3oCowj-DAEGZiyv3z7l-0d2w8LCsgtsZEUjmaNDrGlcz0nEFInczTtKI29lHQ1aY0PJVsPGSw8iR2bK-Q7pc0JA6piQcwFwgU5u3wG5e9vPPx9lCA2yoErr-C2aeq3sV64tUyEmy6IkT3DTmlpZ-ExnGxrDBufijk84mYVucrIneaKesy4HwTiFdYq_4cOv0A9zgUhSQ_MYlb7i-81O9Wy0R7GVt4VCzVM-L8uY8pEaJlLt1HcLJO2Oz1EsY_Jg-ZeRG7D2dO_CpHbJygsRLJwEu9Mf2w8?testcase_id=5395872981712896


Additional requirements: Requires Gestures

Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: jonr...@chromium.org a...@chromium.org mummare...@chromium.org
Labels: Test-Predator-Wrong M-58
Unable to find exact culprit CL, so assigning to few developers who worked on file render_widget_host_view_base.cc. could some one please take a look?.
Thank you
Cc: -jonr...@chromium.org msrchandra@chromium.org
Owner: jonr...@chromium.org
Status: Assigned (was: Untriaged)
This issue looks similar to Bug ID - 662781 which is merged into Bug Id: 661595.
Assigning to the concern owner who worked on the above mentioned bugs.
@jonross -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.
When looking at the original issues, it was found on a flaky clusterfuzz. We never ended up with reproduction steps.

Currently clusterfuzz cannot be ran locally, thus preventing me from reproducing/debugging.

I'll keep an eye on this for now, and once I can repro locally I'll provide a fix.
Project Member

Comment 4 by ClusterFuzz, Mar 30 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5395872981712896 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