When extension fails to load, page becomes unresponsive, freezes
Reported by
jaab...@gmail.com,
May 10 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Example URL: There is not a 100% reproducible step - see below Steps to reproduce the problem: 1. Create a plugin that causes an exception to bubble up (see attached files from Gramerly). 2. Open up any web pste 3. Fire plugin, when it fails to load or bubbles up an exception, the entire tab stops accepting/firing click events, or anything else. Page appears to be "frozen" What is the expected behavior? It would be great if the plug-ins were sandboxed better and not rely upon developers to use proper try/catch, if statements before they do something that will crash the entire experience. What went wrong? In my case, Gramerly failed to load something it needed, and the entire tab no longer accepted inputs when clicking on buttons or other interactions on the page Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 66.0.3359.139 Channel: stable OS Version: OS X 10.13.4 Flash Version: I know that other plug-ins cause this too, it is not just Gramerly. This is why I am escalating to you. Hopefull that somethign can be done to better sandbox these types of errors causing entire tabs/pages/apps to become unresponsive. Afterall, in the view of the end-user, they just believe our web apps are unresponsive and broken. At least an alert indicating which plug-in failed to load would help us manage expectations :)
,
May 10 2018
Yes sorry you are correct it is extensions. Seems like something could be done to at least wrap the injections in a try/catch look so that they don't have this adverse impact. I know that many of the extensions are built by commercial software developers, but I suspect far more are not which leaves a terrible end-user experience. Thanks for the consideration! Jason
,
May 10 2018
,
May 15 2018
,
May 16 2018
jaabuur@ Thanks for the issue. Request you to provide sample file/extensions where this issue can be reproduced which will help in further triaging of the issue. Thanks..
,
Jul 9
Mac triage: WontFix There's no reliable way to detect every injected script in a page, and even if there was, wrapping them in try/catch would hide errors from developers that should be surfaced. The right fix here is to fix the broken extensions. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by woxxom@gmail.com
, May 10 2018