chrome://kill rendering

[Himanshu Joshi]

chrome://kill page is not calling "FrameView::layout" method for rendering, do Chrome follow some other path to render "chrome://kill" page? Do we have any document or link which explains the rendering of pages like chrome://kill 

[PhistucK]

https://code.google.com/p/chromium/codesearch#chromium/src/content/renderer/render_frame_impl.cc&sq=package:chromium&q=kChromeUIKill&type=cs&l=198

☆PhistucK

On Tue, Mar 4, 2014 at 2:40 PM, Himanshu Joshi <h.j...@samsung.com> wrote:

chrome://kill page is not calling "FrameView::layout" method for rendering, do Chrome follow some other path to render "chrome://kill" page? Do we have any document or link which explains the rendering of pages like chrome://kill 

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Arunprasad Rajkumar]

"He's dead, Jim!" is not a WebUI, it is a native rendering. (I used chromium task manager to confirm!)

<BR/>

<Arun/>

[Himanshu Joshi]

How "He's dead, Jim! ... " is rendered as call "layout" method is not called, I added logs to "layout" method which were not displayed.

"layout" logs are displayed when "chrome://setting" etc is used.

[PhistucK]

It is not actually rendered by the navigation.

The sad tab is shown due to the process being terminated (same thing as if you would End task from the Chrome Task Manager).

Totally different code. Search a bit for process termination (or the constant for the sad tab resource) and you will eventually trace the code.

☆PhistucK

[Torne (Richard Coles)]

On 5 March 2014 09:33, Himanshu Joshi <h.j...@samsung.com> wrote:

How "He's dead, Jim! ... " is rendered as call "layout" method is not called, I added logs to "layout" method which were not displayed.

"layout" logs are displayed when "chrome://setting" etc is used.

chrome://settings is what we call a WebUI page - it's a page which is written in HTML and JS, with some C code in Chromium that provides special APIs to the page to enable it to interact with Chrome internals. These pages are rendered by the normal rendering code, in a special type of renderer process that is only allowed to render WebUI pages for security purposes. So, on this kind of page you will see all the normal layout/etc process occurring.

chrome://kill is not a page at all; it's a special URL that just causes the browser code to kill the current renderer process for the foreground tab. Once this happens, the browser detects that the renderer has died, and draws the "He's dead, Jim!" page, which is what happens for all unexpected renderer crashes/exits. This page is *not* HTML at all; it's just text and an image rendered by the browser itself in the same way that the URL bar, tabs, etc are drawn.

It has to be this way, because if the page was HTML, then the renderer responsible for rendering the "the renderer has crashed" page might also crash in some unfortunate circumstance and leave us in a loop forever :)

[Arunprasad Rajkumar]

>>"He's dead, Jim!" is not a WebUI, it is a native rendering. (I used chromium task manager to confirm!)

I mean it is not rendered by blink. It is rendered by Browser Process natively using views/skia/..

Refer sad_tab.{h,cc}, sad_tab_view.cc

<BR/>

<Arun/>

[Himanshu Joshi]

Okey, let me check these files to get some understanding of code flow in case of chrome:kill