845668 - Stand up nested content processes

Status: RESOLVED WONTFIX

(Core :: General, defect)

Description

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Step 1 in getting them working will be getting them launching.  Just like we ran into 5 or 10 little annoying bugs standing up content processes for gonk, I'm sure we'll hit the same thing here.  Needs a little gdb elbow grease.

At this point, I wouldn't expect anything interesting to work, although hopefully we'll be surprised!

Comment 1

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Bare minimum is that a Hello world page should render.

Comment 2

[David Zbarsky (:dzbarsky)]

Attachment: Remove nsFrameLoader::mChildHost

Since you added this.

Comment 3

[Josh Matthews [:jdm]]

Comment on attachment 761904 [details] [diff] [review]
Remove nsFrameLoader::mChildHost

Review of attachment 761904 [details] [diff] [review]:
-----------------------------------------------------------------

ContentParent::ActorDestroy looks like it deals with the lifetime issues that bug 545237 describes, so this looks ok to me.

Comment 4

[David Zbarsky (:dzbarsky)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/c1c441c9edce

Comment 5

[David Zbarsky (:dzbarsky)]

Attachment: Remove nsFrameMessageManager::IsChromeProcess

Comment 6

[Ryan VanderMeulen [:RyanVM]]

Backed out for Windows mochitest-2 crashes as shown in bug 882887.
https://hg.mozilla.org/integration/mozilla-inbound/rev/0c078f228d84

Comment 7

[David Zbarsky (:dzbarsky)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/f178d66490b3

Comment 8

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/f178d66490b3

Comment 9

[David Zbarsky (:dzbarsky)]

Attachment: Don't assume that the chrome registry service in ContentParent is the chrome service.

Comment 10

[Jonathan Watt [:jwatt]]

Ryan, do you think there's anything useful to be taken from this bug, or can it just be dup'ed to bug 1500257 or bug 1429896?

Comment 11

[Ryan Hunt [:rhunt]]

We can definitely close this now with bug 1522579.