You are correct that my information was a bit off, but I suspect the idea wasn't... My apologies if I "sound very authoritative" when I am not.
It seems iexplore.exe does indeed provide the process, along with (at least) the crash handling, adding the text " - Microsoft Internet Explorer" after the web page title, and apparently varies some of the preferences (displayed toolbars at least). It does not seem to affect the rendering of the page, as either iexplore.exe or explorer.exe can do that.
My thought was that the rendering engine may be crashing, without causing the complete application to crash, and without appearing to have crashed. I will stand by that idea. It seems quite plausible to me that every request to render a page might kill any previous thread readering for the window, and start a new one, and this could quite successfully hide rendering engine failures. Other techniques could also mask rendering engine failures.
I guess I really have no idea how one would authoritatively detect if the IE rendering engine has failed. Does anyone?
When saying that Microsoft Internet Explorer didn't crash, does he mean that the window never went away, or that the program iexplore.exe stayed running? I can't prove it, but I suspect that the "IE" window would survive a crash of the rendering engine, because the window is actually provided by explorer.exe, which is the desktop manager.
I also suspect that several of the open source browsers could defend themselves against this kind of crash within a day or two, simply be using a two process model. Personally, I would rather they did not! (I want to see it fail, otherwise I would not know something was wrong.)
Slashdot Mirror
You are correct that my information was a bit off, but I suspect the idea wasn't... My apologies if I "sound very authoritative" when I am not.
It seems iexplore.exe does indeed provide the process, along with (at least) the crash handling, adding the text " - Microsoft Internet Explorer" after the web page title, and apparently varies some of the preferences (displayed toolbars at least). It does not seem to affect the rendering of the page, as either iexplore.exe or explorer.exe can do that.
My thought was that the rendering engine may be crashing, without causing the complete application to crash, and without appearing to have crashed. I will stand by that idea. It seems quite plausible to me that every request to render a page might kill any previous thread readering for the window, and start a new one, and this could quite successfully hide rendering engine failures. Other techniques could also mask rendering engine failures.
I guess I really have no idea how one would authoritatively detect if the IE rendering engine has failed. Does anyone?
I have to ask:
When saying that Microsoft Internet Explorer didn't crash, does he mean that the window never went away, or that the program iexplore.exe stayed running? I can't prove it, but I suspect that the "IE" window would survive a crash of the rendering engine, because the window is actually provided by explorer.exe, which is the desktop manager.
I also suspect that several of the open source browsers could defend themselves against this kind of crash within a day or two, simply be using a two process model. Personally, I would rather they did not! (I want to see it fail, otherwise I would not know something was wrong.)