All Things Techie With Huge, Unstructured, Intuitive Leaps

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.

No comments:

Post a Comment