Extension crashes out of the blue

[GoogleCodeExporter]

Operating System: Windows Vista x32 / Windows 7 x64
Chrome version: 9.0.597.19 beta
Version of android2cloud Chrome extension: 2.0
The server I'm using: own server based on 2.0 app engine code
The Google Account name that I logged in with: private

What I am doing, step-by-step: Just browsing the web normally.

What I expect to see: Nothing.

What I see: Yellow bar drops down and states that the extension has crashed.

How can I get more debugging data on this? When I open Chrome's JavaScript 
console, it is empty.

Original issue reported on code.google.com by lev.ar...@gmail.com on 3 Jan 2011 at 7:55

[GoogleCodeExporter]

You can get debugging by going to chrome://extensions, enabling developer mode, 
and clicking "background.html". The console in that should have some stuff in 
it.

Out of curiosity, how long were you browsing for? A token needs to be renewed 
every four hours, but the current iteration has a bug that causes an infinite 
loop. If you were browsing longer than that, Chrome may have killed the 
extension to escape the infinite loop. A patch is implemented and will be 
rolling out shortly.

Original comment by foran.pa...@gmail.com on 3 Jan 2011 at 8:02

• Changed state: Investigating

[GoogleCodeExporter]

Problem is: After Chrome killed the extension, I can't see it in 
chrome://extensions any more, so I can't click its background.html.

When I re-add the extension, the console for background.html is empty.

Original comment by lev.ar...@gmail.com on 3 Jan 2011 at 10:26

[GoogleCodeExporter]

That is far from helpful on Chrome's part. Sorry. Do you know how long Chrome 
was open when it happened?

Original comment by foran.pa...@gmail.com on 3 Jan 2011 at 10:33

[GoogleCodeExporter]

Not exactly, no. But I'll keep an eye on it. (I've had the crashes on two 
separate machines so I should be able to reproduce them eventually.)

Original comment by lev.ar...@gmail.com on 3 Jan 2011 at 10:35

[GoogleCodeExporter]

If it happens again and you could tell me whether Chrome was open longer than 
four or five hours, that would be awesome. Also, if the update coming tonight 
or in the next couple of days makes the problem not happen for a week or so, 
I'd love an update on that, as well.

Original comment by foran.pa...@gmail.com on 3 Jan 2011 at 10:37

[GoogleCodeExporter]

OK, it is now 09:00 here and I just re-added the extension and ran through the 
setup agent. Now waiting to see when it crashes. (This entry shall serve as 
reminder of when I started.)

Original comment by lev.ar...@gmail.com on 4 Jan 2011 at 8:01

[GoogleCodeExporter]

11:00: The extension crashed. I cannot exactly trace when, but definitely under 
the 4 hour mark.

Other annoying bit: I had the console open, thinking I could trick Chrome into 
letting me see what's going on when the extension crashes, but then I went to 
check on the extension (opened the Extensions window), Chrome closed the 
console window! Very unhelpful.

Will now try again, this time I'll capture the console window before checking 
the Extension!

Original comment by lev.ar...@gmail.com on 4 Jan 2011 at 10:10

[GoogleCodeExporter]

13:15: crashed again. Seems to happen every 2 hours here. The console window 
vanished again but I did see some errors related to our proxy, so maybe 
reproducing the error here does not work and I have to retry at home where my 
other PC has the issue and isn't behind a restrictive proxy.

Original comment by lev.ar...@gmail.com on 4 Jan 2011 at 12:16

[GoogleCodeExporter]

Issue 58 has been merged into this issue.

Original comment by foran.pa...@gmail.com on 5 Jan 2011 at 4:28

[GoogleCodeExporter]

Hmm.. Let me know if the patch I push out doesn't fix this. Look for it in the 
next couple of days.

Original comment by foran.pa...@gmail.com on 5 Jan 2011 at 4:29

[GoogleCodeExporter]

Updated the extension... we'll see how it holds now.

On a sidenote: After running through the setup guide again, the extension 
opened all the links I had previously sent to the 2.0 android2cloud server. Is 
that normal?

Original comment by lev.ar...@gmail.com on 6 Jan 2011 at 1:54

[GoogleCodeExporter]

Been running 2.0.2 all day and have not seen the memory leak or the crash so 
far. I think this can be closed.

Original comment by lev.ar...@gmail.com on 7 Jan 2011 at 5:18

[GoogleCodeExporter]

Awesome, thanks. :) If it reappears, let me know, and we'll reopen the ticket.

Original comment by foran.pa...@gmail.com on 7 Jan 2011 at 9:26

• Changed state: Fixed