Chrome Canary - Wonderful but flawed - Just like me

(click on pic for larger image)

"He's dead, Jim!".  That's what Chrome Canary tells me every time I try to play a youtube video. Chrome Canary and Windows 7 doesn't let youtube work. You always get the purple screen of death saying that Chrome ran out of memory.

When you download Chrome ( from here: https://www.google.com/chrome/browser/canary.html ), the splash page warns you.  It says" Get the Bleeding Edge of the Web".  It says that this browser is not for the faint-hearted and it crashes regularly.

The splash page also says: "Google Chrome Canary has the newest of the new Chrome features.
Be forewarned: it's designed for developers and early adopters, and can sometimes break down completely."

So why did I get it? I am a developer among other things. When I develop Android, and I have an app with a web widget, often things like javascript breaks down.  These kind of web errors are often not reported in the Software Development Kit.  Only Java errors that throw exceptions are regularly recorded.  So when your app goes Islamic Terrorist Irrational on you, you can connect the USB cord to the Android device, type in chrome://inspect and click on devices, and you can get an idea of why you app has gone ape-crap or bat-crap crazy. A javascript console can be a very helpful thing.

Other features is that Chrome Canary is blazing fast.  In fact the only negative so far, is that it craps out with youtube and win7.  I am willing to bet though, that it doesn't crap out in a Chromebook.

More Chrome Grief

More Google Chrome browser grief.  I merely refreshed a Yahoo mail page and Google Chrome crashed.  Was it Yahoo's fault or Google's?  Who knows.  This is what the message said:

Unhandled exception at 0x77de15de in chrome.exe: 0xC0000374: A heap has been corrupted.

Then it asked me if I wanted to debug it.  Since I have a debugger on board, I said sure.  Here is what the trail looks like:

77DE15B3  nop              
77DE15B4  mov         eax,12Eh 
77DE15B9  xor         ecx,ecx 
77DE15BB  lea         edx,[esp+4] 
77DE15BF  call        dword ptr fs:[0C0h] 
77DE15C6  add         esp,4 
77DE15C9  ret         18h  
77DE15CC  mov         eax,12Fh 
77DE15D1  xor         ecx,ecx 
77DE15D3  lea         edx,[esp+4] 
77DE15D7  call        dword ptr fs:[0C0h] 
77DE15DE  add         esp,4 

And it crapped out at 77DE15DE.  Here it is adding esp a stack pointer to 4.  A corrupted heap means several things.  One could be that the stack pointer has been deallocated, or destroyed, or not set.  Whatever the cancer in the stack was, it caused the whole thing to blow up.

The ironic thing is that the exception was not handled.  This means that there was no accounting for error in the code.  At a high level, this is sloppy coding.  As previously iterated, Chrome is starting to lose its shine.  It turns out that the Google programming machine is not infallible as they like to believe.

Blogger -- Image Upload Headaches with Google Chrome

I rarely shut my laptop down.  I have two versions of Eclipse running on it (one to run a Tomcat project) and one purely for Android that uses some of the Tomcat capabilities.  In addition, it acts as a MySQL server, and I read email and post to Twitter, and monitor various websites all at the same time.

A couple of days ago, Google Blogger image upload stopped working.  I couldn't upload an image to my blog.  Instead of the file selection box to pick an image from my computer, it says "In order to select an image from your online storage, please sign in".  I figured, what the heck, I will re-sign in with my Google credentials and see what happens.

 When I try to sign in, I get:
There was an error!
Details:
The feature you requested is currently unavailable. Please try again later.

I figured that this was a temporary thing.  I set it aside and for two days nada.  I finally decided to solve this this morning.  I shut down Chrome and restarted.  Nothing.  I rebooted the laptop.  Nothing.



I started Chrome, went to the three parallel bars in the corner, the menu and selected:

Tools > Clear Browsing Data
I cleared all of the browsing data, shut down Chrome, re-started it,
I then went to Settings and the content settings and enabled third party cookies.
 After all of that, it started to work again.  I can now upload images from my computer.

Hope this helps someone.