Chrome Browser Crashes

I had Chrome go down again.  It told me that a heap has been corrupted.  I have a debugger, so I got the exact place where the Chrome Browswer died.  Here are the gory details:


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

Debugger information:  The heap:
771815B4  mov         eax,12Eh 
771815B9  xor         ecx,ecx 
771815BB  lea         edx,[esp+4] 
771815BF  call        dword ptr fs:[0C0h] 
771815C6  add         esp,4 
771815C9  ret         18h  
771815CC  mov         eax,12Fh 
771815D1  xor         ecx,ecx 
771815D3  lea         edx,[esp+4] 
771815D7  call        dword ptr fs:[0C0h] 
771815DE  add         esp,4 

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.

Browser Plug-ins that Would Sell Like Crazy

I am not a browser plug-in developer, but I do know of two browser plug-ins that would make their coders millionaires. It would be a plug-in with a semi-transparent layer with two controls -- "MUTE" and "FAST FORWARD". And it would be an intelligent plug-in. It would hide itself on most web pages, but does a quick look-ahead to see if the web page has auto-play media, either audio or audio/video. If so, the layer would materialize.

The user would have the ability to mute the sound of auto-play and for sites that put in advertising videos before the video that you actually click on to watch, it would either fast forward or eliminate it.

The web has become worse than TV for advertising. On TV you get at least 5-10 minutes of content for a thirty-second advert. On the web, if you want to watch 5 one minute clips, you get a thirty second advert with each clip.

There are programmers smart enough to build these anti-ads plugins. I am waiting.