Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(36)

Unified Diff: chrome/browser/prerender/prerender_manager.cc

Issue 6691040: Allow prerendering in single-process mode. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/
Patch Set: Slightly better comment Created 9 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/browser/prerender/prerender_manager.cc
===================================================================
--- chrome/browser/prerender/prerender_manager.cc (revision 80344)
+++ chrome/browser/prerender/prerender_manager.cc (working copy)
@@ -155,9 +155,12 @@
// have to use an existing one. We do not want prerendering to happen in
// a shared process, so that we can always reliably lower the CPU
// priority for prerendering.
+ // In single-process mode, ShouldTryToUseExistingProcessHost() always returns
+ // true, so that case needs to be explicitly checked for.
// TODO(tburkard): Figure out how to cancel prerendering in the opposite
// case, when a new tab is added to a process used for prerendering.
- if (RenderProcessHost::ShouldTryToUseExistingProcessHost()) {
+ if (RenderProcessHost::ShouldTryToUseExistingProcessHost() &&
+ !RenderProcessHost::run_renderer_in_process()) {
// Only record the status if we are not in the control group.
if (!IsControlGroup())
RecordFinalStatus(FINAL_STATUS_TOO_MANY_PROCESSES);
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698