CentBrowser Forum
BUG? Single Renderer Process - Printable Version

+- CentBrowser Forum (https://www.centbrowser.net/en)
+-- Forum: Product Related (https://www.centbrowser.net/en/forumdisplay.php?fid=1)
+--- Forum: Bugs & Suggestions (https://www.centbrowser.net/en/forumdisplay.php?fid=4)
+--- Thread: BUG? Single Renderer Process (/showthread.php?tid=1071)



BUG? Single Renderer Process - peefour - 06-08-2016

I enabled Single Renderer Process, but each tab has still its own process.
is this normal?

tx


RE: BUG? Single Renderer Process - Admini - 06-10-2016

That feature was removed from Cent because of side effect.
Now we only have Single Extension Process option, it means all extensions share the same process.
If you still want Single Render Process, you can create a shortcut and append this command line(--renderer-process-limit=1) to it.
Please remember this command line shouldn't be used in the Startup Command Line option.


RE: BUG? Single Renderer Process - peefour - 06-11-2016

(06-10-2016, 03:25 PM)CentBrowser Wrote: That feature was removed from Cent because of side effect.
Now we only have Single Extension Process option, it means all extensions share the same process.
If you still want Single Render Process, you can create a shortcut and append this command line(--renderer-process-limit=1) to it.
Please remember this command line shouldn't be used in the Startup Command Line option.

hello,

thanks for your answer!


RE: BUG? Single Renderer Process - peefour - 06-13-2016

(06-11-2016, 05:24 PM)peefour Wrote:
(06-10-2016, 03:25 PM)CentBrowser Wrote: That feature was removed from Cent because of side effect.
Now we only have Single Extension Process option, it means all extensions share the same process.
If you still want Single Render Process, you can create a shortcut and append this command line(--renderer-process-limit=1) to it.
Please remember this command line shouldn't be used in the Startup Command Line option.

hello,

thanks for your answer!

Hi,

I tried this command in the shortcut target : C:\Users\me\AppData\Local\CentBrowser\Application\chrome.exe --renderer-process-limit=1
The Single Extension Process option is also activated in the browser settings.
but I still have many processes. (each new tab has its own process, and the plugins too.
all extensions are grouped in one process,and the 'not empty tabs' are grouped too, which is good
Is this the normal behaviour of this option?

Thanks!


RE: BUG? Single Renderer Process - Admini - 06-14-2016

(06-13-2016, 03:37 PM)peefour Wrote: Hi,

I tried this command in the shortcut target : C:\Users\me\AppData\Local\CentBrowser\Application\chrome.exe --renderer-process-limit=1
The Single Extension Process option is also activated in the browser settings.
but I still have many processes. (each new tab has its own process, and the plugins too.
all extensions are grouped in one process,and the 'not empty tabs' are grouped too, which is good
Is this the normal behaviour of this option?

Thanks!

Yes, that command line also doesn't promise only one renderer process.
But it can reduce renderer process count as many as possible.
For example, in general cases aaa.com and aab.com are in seperate processes.
With this command line, they may be combined into one process.
You can check this by Task Manager in the browser.
One more thing, Chrome/Chromium may force to create new processes in some cases.
So you may still see many processes, but already less than its normal behavior.


RE: BUG? Single Renderer Process - peefour - 06-16-2016

(06-14-2016, 06:45 PM)CentBrowser Wrote:
(06-13-2016, 03:37 PM)peefour Wrote: Hi,

I tried this command in the shortcut target : C:\Users\me\AppData\Local\CentBrowser\Application\chrome.exe --renderer-process-limit=1
The Single Extension Process option is also activated in the browser settings.
but I still have many processes. (each new tab has its own process, and the plugins too.
all extensions are grouped in one process,and the 'not empty tabs' are grouped too, which is good
Is this the normal behaviour of this option?

Thanks!

Yes, that command line also doesn't promise only one renderer process.
But it can reduce renderer process count as many as possible.
For example, in general cases aaa.com and aab.com are in seperate processes.
With this command line, they may be combined into one process.
You can check this by Task Manager in the browser.
One more thing, Chrome/Chromium may force to create new processes in some cases.
So you may still see many processes, but already less than its normal behavior.

 that is a very clear explanationSmile
thank you very much