Crash in std::map<std::string, std::map<std::string, std::list<extensions::QuotaLimitHeur |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4549090316910592 Fuzzer: meacer_chromebot_extensions Job Type: linux_asan_chrome_chromeos Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000080 Crash State: std::map<std::string, std::map<std::string, std::list<extensions::QuotaLimitHeur extensions::QuotaService::Assess extensions::ExtensionFunctionDispatcher::DispatchWithCallbackInternal Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=415049:415582 Minimized Testcase (71.01 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97XmqxQ1zoQE0G-1fuuiu8DwvpxWLa2fCI0Zyyal3Mc2iaONWuw7ZEypc7T7Eysf_0Q6V_pM8qqDgiE4ecGBxEjApFRs8j9uV-YS9hFsAm2_i83TdQNmy6kt_5sFfJw7LPJN0Xu_zNmbb-CXxxr5SATj8qzKgVMtAcNKViZvduXIbpgTdE?testcase_id=4549090316910592 Issue manually filed by: mummareddy See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Sep 21 2016
Gentle ping!
,
Sep 22 2016
I could not repro the crash this locally, any clue on how to reproduce the behavior? It could be my CL or not, I'm not sure.
I loaded the extension from the minimized testcase. Then I opened 25 tabs to all of the fuzz-extension-run-*.html files, but no luck. I've also enabled flash [1].
I've tried both linux build and linux chromeos build.
@meacer can you help since the fuzzer name contains your username.
[1] command line:
'--ppapi-flash-path=/usr/local/google/home/lazyboy/.config/google-chrome-beta/PepperFlash/23.0.0.166/libpepflashplayer.so --ppapi-flash-version=23.0.0.166'
,
Nov 16 2016
Was able to reproduce this locally this time, it seems like a bug/race in --load-extension, if specified extension fails to load, ExtensionSystem::quota_service() returns null for extension functions coming from a component extension. For my repro the component extension was Files app.
,
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
,
Dec 14 2016
This is already fixed but commit bot didn't add the CL: r434009: https://codereview.chromium.org/2520833003/ Marking this as fixed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mummare...@chromium.org
, Aug 31 2016Labels: findit-wrong M-55 Te-Logged
Owner: lazyboy@chromium.org
Status: Assigned (was: Untriaged)