| Index: chrome/browser/renderer_host/test/render_process_host_browsertest.cc
|
| diff --git a/chrome/browser/renderer_host/test/render_process_host_browsertest.cc b/chrome/browser/renderer_host/test/render_process_host_browsertest.cc
|
| index 04a7c5ff092ce5b45fdd3cb540f4e51a51cf2d8e..152b646924348f2d5f0314ceb1d03d708ef634a9 100644
|
| --- a/chrome/browser/renderer_host/test/render_process_host_browsertest.cc
|
| +++ b/chrome/browser/renderer_host/test/render_process_host_browsertest.cc
|
| @@ -183,9 +183,7 @@ IN_PROC_BROWSER_TEST_F(RenderProcessHostTest, DevToolsOnSelfInOwnProcess) {
|
| // sharing behaves correctly. In particular, this test is verifying that even
|
| // when we hit the max process limit, that renderers of each type will wind up
|
| // in a process of that type, even if that means creating a new process.
|
| -// TODO(erikkay) crbug.com/43448 - disabled for now until we can get a
|
| -// reasonable implementation in place.
|
| -IN_PROC_BROWSER_TEST_F(RenderProcessHostTest, DISABLED_ProcessOverflow) {
|
| +IN_PROC_BROWSER_TEST_F(RenderProcessHostTest, ProcessOverflow) {
|
| // Set max renderers to 1 to force running out of processes.
|
| RenderProcessHost::SetMaxRendererProcessCount(1);
|
|
|
|
|