Closed Bug 661673 Opened 13 years ago Closed 13 years ago

don't start child process when browser.tabs.remote is false

Categories

(Firefox for Android Graveyard :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 7

People

(Reporter: dougt, Assigned: dougt)

Details

(Whiteboard: QA?)

Attachments

(2 files, 1 obsolete file)

Attached patch patch v.1Splinter Review
don't start child process when browser.tabs.remote is false
Attachment #536984 - Flags: review?(mbrubeck)
Comment on attachment 536984 [details] [diff] [review]
patch v.1

Sounds fine. The child process will start on it's own if we need it for some reason. We only manually load it here so the app can start without the overhead, but then the process is ready and waiting for the first remote tab that opens.
Attachment #536984 - Flags: review?(mbrubeck) → review+
Keywords: checkin-needed
Attached file patch to push (obsolete) —
Attachment #537074 - Attachment is obsolete: true
Attachment #537074 - Attachment is patch: false
Attached patch patch to pushSplinter Review
Target Milestone: --- → Firefox 7
How can I verify this?
Flags: in-litmus?(kbrosnan)
Whiteboard: QA?
Flags: in-litmus?(kbrosnan)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: