Re: [crx] Extension Crashing on Update

[PhistucK]

Enable logging, start Chrome and after the extension crashed and post the resulting log file (check for personal information first maybe, but I do not think it has any).

☆PhistucK

On Wed, Jul 18, 2012 at 12:25 PM, Simon Knott <knott...@gmail.com> wrote:

I have developed an extension which appears to crash in a completely reproducible manner when it's updated, popping up a little notification balloon asking me to click it and reload it, and I am completely in the dark as to how to debug the problem.  I've got crash dumps enabled, but nothing appears in chrome://crashes.

I've also tested updating the extension on Canary and have exactly the same problem.  Could someone please enlighten me as to how I can debug and resolve this issue?

Cheers,

Simon

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/bdocdRyFbl0J.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

[Simon Knott]

Thanks for the info.

On Friday, 20 July 2012 21:19:40 UTC+1, PhistucK wrote:

Enable logging, start Chrome and after the extension crashed and post the resulting log file (check for personal information first maybe, but I do not think it has any).

☆PhistucK

On Wed, Jul 18, 2012 at 12:25 PM, Simon Knott <knott...@gmail.com> wrote:

I have developed an extension which appears to crash in a completely reproducible manner when it's updated, popping up a little notification balloon asking me to click it and reload it, and I am completely in the dark as to how to debug the problem.  I've got crash dumps enabled, but nothing appears in chrome://crashes.

I've also tested updating the extension on Canary and have exactly the same problem.  Could someone please enlighten me as to how I can debug and resolve this issue?

Cheers,

Simon

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/bdocdRyFbl0J.

To post to this group, send email to chromium-extensions@chromium.org.
To unsubscribe from this group, send email to chromium-extensions+unsub...@chromium.org.

[PhistucK]

Then try to get the log from your users, it might help.

☆PhistucK

On Thu, Aug 2, 2012 at 4:07 AM, Michael Hart / Awesome New Tab Page <m...@antp.co> wrote:

I get frequent reports of crashing on update days for Awesome New Tab Page.

Unfortunately, it rarely happens to me making logging it nearly impossible.

It's incredibly frustrating to get negative reviews that are pretty much "amazing extension, but crashes frequently".

On Wednesday, July 18, 2012 5:25:02 AM UTC-4, Simon Knott wrote:

I have developed an extension which appears to crash in a completely reproducible manner when it's updated, popping up a little notification balloon asking me to click it and reload it, and I am completely in the dark as to how to debug the problem.  I've got crash dumps enabled, but nothing appears in chrome://crashes.

I've also tested updating the extension on Canary and have exactly the same problem.  Could someone please enlighten me as to how I can debug and resolve this issue?

Cheers,

Simon

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/hr_FisFV0g8J.

To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.

[Michael Hart / Awesome New Tab Page]

Here's a log in Verbose: http://h4r7.me/FvEw+

I tried to clear seconds before hitting update and stop it seconds after the crash.

I can reproduce 100% of the time using a virtual machine snapshot.

[PhistucK]

Can you go to chrome://crashes/ and if you identify the crash there (I am not sure it would be there at all), file an issue?

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/_i3vvNeC3YwJ.

[Michael Hart / Awesome New Tab Page]

Nope :( Nothing listed for today. Most recent crash in the list was weeks ago.

[PhistucK]

Can you check the logs and assist somehow? Thank you!

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/_i3vvNeC3YwJ.

[Michael Hart / Awesome New Tab Page]

It's possibly worth noting that I've long suspected that the crashing was caused by Awesome New Tab Page's extensive use of the chrome.extension.sendRequest/chrome.extension.sendMessage API.

Awesome New Tab Page is an extensible extension, so it communicates to other Chrome extensions to find widgets that work with it. To do this, it has to attempt to send a message to all installed extensions (I call this process "poke") and then listens for responses using chrome.extension.onRequestExternal.addListener/chrome.extension.onMessageExternal.addListener (I use this over sendRequest/sendMessage response so that I can validate the sender).

chrome.extension.sendRequest returns an error in the background for every extension it fails to connect to (most extensions don't have a listener). chrome.extension.sendRequest is now deprecated, being renamed to chrome.extension.sendMessage (same for onRequestExternal, which is now onMessageExternal). This API doesn't seem to cause these errors, but unfortunately isn't backwards compatible with the previous API (I made a bug report about this here crbug.com/139368). Unfortunately, I don't control the extensions 3rd party developers make, so I have to support both for a period of time until most developers can update their "poke" code.

(Sidenote: This happened before the dual stacking the new and old API just as frequently as before, from what I can tell based on user complaints. It's happened since ANTP was first released late 2011).

Anyway, I could be and probably am completely wrong; it may not be related to those APIs at all. In the provided logs, that Chrome install only had Awesome New Tab Page installed and was, roughly, a fresh install (no other extensions to fail to connect to). It's just what I've always suspected, considering that's most of what makes Awesome New Tab Page vastly different from most other Chrome extensions.

I'd be happy to help as much as possible, though. I greatly desire for a day where extensions don't crash. ;)

On Thursday, August 2, 2012 2:33:31 AM UTC-4, PhistucK wrote:

Can you check the logs and assist somehow? Thank you!

☆PhistucK

On Thu, Aug 2, 2012 at 9:05 AM, Michael Hart / Awesome New Tab Page <m...@antp.co> wrote:

Here's a log in Verbose: http://h4r7.me/FvEw+

I tried to clear seconds before hitting update and stop it seconds after the crash.

I can reproduce 100% of the time using a virtual machine snapshot.

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/_i3vvNeC3YwJ.

To post to this group, send email to chromium-extensions@chromium.org.
To unsubscribe from this group, send email to chromium-extensions+unsub...@chromium.org.

[Michael Hart / Awesome New Tab Page]

I made a issue about this here:  http://crbug.com/140292 

Thanks for the help, PhistucK ;)