Issue metadata
Sign in to add a comment
|
Checker Plus for Google Drive crashes often
Reported by
jasonsav...@gmail.com,
Dec 22 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Install the Checker Plus for Google Drive extension 2. Wait a few hours and click the toolbar button to open the popup window 3. What is the expected behavior? Opens the popup window What went wrong? Sometimes the popup window opens for only a split second and then crashes. The standard crash notification to relaunch the extension is then displayed and the popup window will work again for a few more hours. WebStore page: https://chrome.google.com/webstore/detail/checker-plus-for-google-d/pppfmbnpgflleackdcojndfgpiboghga Did this work before? Yes 54 Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Dec 30 2016
I confirm that all 3 of my Chrome extensions have been crashing regularly since Chrome 55. The reviews and my uninstall user surveys are also revealing this. The extensions are: Checker Plus for Gmail Checker Plus for Google Calendar Checker Plus for Google Drive (The most frequent one) I believe this is my recent crash id from Checker Plus for Google Drive: Crash ID ff63ea5c-ae05-4144-84ad-4251e6159b7b (Server ID: 25929e6080000000) Automatically reported Friday, December 30, 2016 at 8:26:35 AM Details for possible leads: - The crashes all occur a split second after opening the popup windows - I use Polymer in all my popup windows - This issue has also surfaced in Chrome 55 - perhaps it's related to the crashes: https://bugs.chromium.org/p/chromium/issues/detail?id=649942
,
Dec 31 2016
This morning my Checker Plus for Google Calendar crashed here is the id for that one: Crash ID 2fe3bce6-b36f-4239-a8f5-1cb5a7f9f25e (Server ID: a97c9b6080000000)
,
Jan 9 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 10 2017
2 consecutive crashes just now (note: OS is macOS 10.12.2, Chrome Version 55.0.2883.95 (64-bit)) Crash ID 2dbcd359-e92f-4372-a00c-6015ac08cb54 (Server ID: 7c9a592480000000) Crash ID e5ddd2e3-6133-4696-b526-4808031498a3 (Server ID: 1e870b2480000000)
,
Jan 13 2017
Thanks for the crash ID's, By comparing the stack trace of the provided report ID issue looks similar to bug 663302, Hence merging in to it. Feel free to undupe if it's a different issue. Thanks!
,
Jan 13 2017
I don't have permissions to view 663302 so I can't verify and follow
,
Jan 13 2017
Regardless, yesterday I encountered 5 consecutive crashes Crash ID b94cd182-a2e5-4346-8f32-774221e157c7 Crash ID b5634f91-812e-4cf1-ae72-3947f6fb306e Crash ID 5be70de3-e08d-4de9-8837-599f0d39050a Crash ID bde2952b-92d1-4588-bcb3-16909aac3310 Crash ID 0c2a22f6-60b8-435a-8d6c-4e42adb0c67c (Server ID: 5c6e30b080000000)
,
Feb 2 2017
The issue seemed to have been resolved temporarily with the new Chrome Stable 56 (56.0.2924.76). But, with the latest Chrome Stable update v56.0.2924.87 I am encountering the issue again. My assumption is might have to do with this change mentioned in the Chrome update log: scheduler: Make DOM window event tasks unthrottled This patch avoids throttling events that are routed via DOMWindowEventQueue. This affects a handful of window-related events, the most important ones being IndexedDB events. It turns out many web pages (e.g., Google Docs) rely on IndexedDB transactions to be relatively fast and start encountering errors if they are throttled too aggressively while a tab is in the background. BUG= 675372 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by brajkumar@chromium.org
, Dec 30 2016Labels: Stability-Crash Needs-Feedback