Issue metadata
Sign in to add a comment
|
CHECK failed: false in browser_process_impl.cc |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5721920886013952 Fuzzer: meacer_extension_apis Job Type: linux_asan_chrome_mp Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: CHECK failed: false in browser_process_impl.cc Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_mp&range=144946:145047 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95q3scJVCf3XOwFPWbgD3T6QdhSYCnhoNTC_fmbXIVa84-SeeBm19CTohiCkhwPgfYZ5w0QeuJCP_rh9r7sgFQQWwq4HQs3zpjs4f9dN-kvg-pAF8x9uiyjynTqiZA-RKjm1zL6ZiseA4JrANScYts4fYlNTg Filer: manoranjanr See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Mar 25 2016
Probably some sort of race condition. According to the trace it happened on a release where my changes didn't land. I think the extension code doesn't check that we're not shutting down somewhere. I'll have a look next week to see who should take it over.
,
Mar 25 2016
Thank you so much for the update.
,
Apr 7 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 manoranj...@chromium.org
, Mar 24 2016Owner: dgn@chromium.org
Status: Assigned (was: Available)