Reliable crash on Google internal dashboard w/ Dashlane extension installed |
||||
Issue descriptionChrome Version : Version 56.0.2924.87 URLs (if applicable) : see below <b>OS version : <from About This Mac></b> Behavior in Safari (if applicable): Behavior in Firefox (if applicable): What steps will reproduce the problem? (0) Install dashlane extension in Chrome. You don't need the Mac OS client running; just having the extension installed is enough. (1) You will need to get access to the dashboard. Create a Ganpati membership proposal to mdb/magiceye-dashboard-viewers, and in your justification you can cite b/36904826 or to have bpearcy@ review your access. (3) Once you have access, visit the following page and wait ~5 seconds to see the crash. https://data.corp.google.com/sites/magiceye/curated_multi_product/ What is the expected result? Don't crash! What happens instead? Crash!
,
Apr 6 2017
Here are two: one from just now, and one from this morning. Crash ID d334f564-8d12-4c95-bb3d-cd4f1fc33165 (Server ID: e498a48a10000000) Crash report captured on Thursday, April 6, 2017 at 4:28:33 PM, uploaded on Thursday, April 6, 2017 at 4:28:38 PM Crash ID d334f564-8d12-4c95-bb3d-cd4f1fc33165 (Server ID: e498a48a10000000) Crash report captured on Thursday, April 6, 2017 at 4:28:33 PM, uploaded on Thursday, April 6, 2017 at 4:28:38 PM
,
Apr 6 2017
Thank you for providing more feedback. Adding requester "avi@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 6 2017
0x00000001096abf15 (Google Chrome Framework -V8Initializer.cpp:105 ) blink::reportOOMErrorInMainThread(char const*, bool) 0x00000001053adae6 (Google Chrome Framework -api.cc:416 ) v8::Utils::ReportOOMFailure(char const*, bool) 0x00000001053ada88 (Google Chrome Framework -api.cc:379 ) v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) 0x0000000105774b19 (Google Chrome Framework -factory.cc:503 ) v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) 0x00000001058b1113 (Google Chrome Framework -objects.cc:2481 ) v8::internal::String::SlowFlatten(v8::internal::Handle<v8::internal::ConsString>, v8::internal::PretenureFlag) 0x00000001058d5616 (Google Chrome Framework -objects-inl.h:3664 ) v8::internal::String::IndexOf(v8::internal::Isolate*, v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::String>, int) 0x00000001058d54ed (Google Chrome Framework -objects.cc:11321 ) v8::internal::String::IndexOf(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>) 0x0000000105ab205d (Google Chrome Framework -runtime-strings.cc:95 ) v8::internal::Runtime_StringIndexOf(int, v8::internal::Object**, v8::internal::Isolate*) This is an OOM crash. The page's JavaScript uses too much memory.
,
Apr 6 2017
,
Apr 6 2017
Either the page, or Dashlane's extension. Given that you said that it requires Dashlane, it might be them.
,
Apr 6 2017
Disabling the Dashlane extension seems to prevent this OOM crash on the page. Do Chrome extensions share the memory limit with the page itself? i.e., would any other Chrome extension that requires the same amount of memory as Dashlane cause this crash as well? Thanks! Brandon
,
Apr 6 2017
Extensions inject JavaScript into the page, so if the JavaScript takes a ton of memory it's the host page that crashes. Contact the Dashlane people to see if they can help. |
||||
►
Sign in to add a comment |
||||
Comment 1 by a...@chromium.org
, Apr 6 2017