You are not logged in.

#1 2013-08-18 15:51:07

Dashius
Member
Registered: 2013-08-09
Posts: 8

Little issue with chromium

Chrome Version: Version 28.0.1500.95
Extensions:
Google Apps Script 1.3
Pocket (formerly Read It Later) 1.5.5
Turn Off the Lights 2.2.0.21

I'm not sure if this is the right place to post this, but maybe someone has seen or noticed this before and I'd rather post here than on th chrome forums, because I am certain they will just discard the issue by blaming it on a lack of knowledge on the OS sooner than later. that said...

*******************************

Hello, I've noticed that whenever I open a chromium window I get 3 instances of chromium in my processes list.

That is to say, for each tab that is open on chromium, I will have 3 chromium processes with a distinct PID. Killing any of them will close chromium, of course, but the question is, why?

Isn't it supposed to be just one process per tab? Unless there is something I don't know about how chromium is currently handling it's processes... Which is why I'm here... Could it be the plugins I am using? Like pepper-flash, creating another instance of chromium for some reason I'm not aware of?

Looking at the output of ps aux | grep chromium right now, I get this:

user    1312  3.9  5.1 1795300 199076 ?      Sl   08:06   0:31 /usr/lib/chromium/chromium --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.96
user    1314  0.0  0.2 373048  8016 ?        S    08:06   0:00 /usr/lib/chromium/chromium --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.96
user    1315  0.0  0.0   6380   392 ?        S    08:06   0:00 /usr/lib/chromium/chromium-sandbox /usr/lib/chromium/chromium --type=zygote --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.96
user    1316  0.0  0.6 416536 24864 ?        S    08:06   0:00 /usr/lib/chromium/chromium --type=zygote --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.96
user    1320  0.0  0.1 171004  4608 ?        S    08:06   0:00 /usr/lib/chromium/nacl_helper_bootstrap /usr/lib/chromium/nacl_helper --reserved_at_zero=0x0000000000000000 --r_debug=0x0000000000213000
user    1321  0.0  0.1 424732  7360 ?        S    08:06   0:00 /usr/lib/chromium/chromium --type=zygote --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.96
user    1359  0.0  0.9 1213184 35024 ?       Sl   08:06   0:00 /usr/lib/chromium/chromium --type=renderer --lang=en-US --force-fieldtrials=ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender/PrerenderEnabled/PrerenderLoggedInPredictor/Enabled/UMA-New-Install-Uniformity-Trial/Control/UMA-Session-Randomized-Uniformity-Trial-5-Percent/default/UMA-Uniformity-Trial-1-Percent/group_95/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-20-Percent/group_02/UMA-Uniformity-Trial-5-Percent/group_10/UMA-Uniformity-Trial-50-Percent/default/ --extension-process --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.96 --disable-accelerated-2d-canvas --disable-accelerated-video-decode --channel=1312.1.1313231592
user    1777  3.4  3.4 1297132 134984 ?      Sl   08:07   0:23 /usr/lib/chromium/chromium --type=renderer --lang=en-US --force-fieldtrials=ForceCompositingMode/disable/InfiniteCache/No/Prefetch/ContentPrefetchPrefetchOff/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLoggedInPredictor/Enabled/UMA-New-Install-Uniformity-Trial/Control/UMA-Session-Randomized-Uniformity-Trial-5-Percent/default/UMA-Uniformity-Trial-1-Percent/group_95/UMA-Uniformity-Trial-10-Percent/group_03/UMA-Uniformity-Trial-20-Percent/group_02/UMA-Uniformity-Trial-5-Percent/group_10/UMA-Uniformity-Trial-50-Percent/default/ --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.8.800.96 --disable-accelerated-2d-canvas --disable-accelerated-video-decode --channel=1312.10.1085352894
user    2123  0.1  1.0 579036 39332 ?        Sl   08:09   0:00 /usr/lib/chromium/chromium --type=gpu-process --channel=1312.15.1070582340 --supports-dual-gpus=false --gpu-driver-bug-workarounds=0,6,20 --gpu-vendor-id=0x8086 --gpu-device-id=0x2a42 --gpu-driver-vendor=Mesa --gpu-driver-version=9.1.6
user    2127  0.0  0.2 472964  7928 ?        S    08:09   0:00 /usr/lib/chromium/chromium --type=gpu-process --channel=1312.15.1070582340 --supports-dual-gpus=false --gpu-driver-bug-workarounds=0,6,20 --gpu-vendor-id=0x8086 --gpu-device-id=0x2a42 --gpu-driver-vendor=Mesa --gpu-driver-version=9.1.6


However, looking at top, I have 3 instances of chromium (sometimes just 2, but even then, we want 1 per tab), and only one tab open...

Any light anyone could shed on this is appreciated. Maybe it is just something silly I am missing in terms of information...

Offline

#2 2013-08-18 15:55:11

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,549
Website

Re: Little issue with chromium

Where did you get the idea that there'd be only one process per tab?  One of chrom{e,ium}s claims is that each tab has separate processes; but I've never heard it claimed that each tab has only one process.  It's just multithreading.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2013-08-19 04:31:23

Dashius
Member
Registered: 2013-08-09
Posts: 8

Re: Little issue with chromium

Trilby wrote:

Where did you get the idea that there'd be only one process per tab?  One of chrom{e,ium}s claims is that each tab has separate processes; but I've never heard it claimed that each tab has only one process.  It's just multithreading.

I may have heard it at the university last semester, but I wasn't sure about the validity of the claim...

Hence the thread inquiring about whether or not that is normal, but I appreciate your input.

Offline

#4 2013-08-19 04:45:43

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,414

Re: Little issue with chromium

Chrom{e,ium} was (one of?) the first browser to actually create a separate instance for each tab.  So although that model used slightly more ram the advantage was much more stability.  If you had one tab that totally froze on you, you could close/kill just that tab and the rest would happily keep running.  Now a separate instance does not mean that each tab will only produce one thread.  Having multiple threads is not a bad thing, and actually is probably better splitting tasks to increase efficiency. 

In other words.  This is normal.

Offline

#5 2013-08-19 04:48:01

Dashius
Member
Registered: 2013-08-09
Posts: 8

Re: Little issue with chromium

WonderWoofy wrote:

Chrom{e,ium} was (one of?) the first browser to actually create a separate instance for each tab.  So although that model used slightly more ram the advantage was much more stability.  If you had one tab that totally froze on you, you could close/kill just that tab and the rest would happily keep running.  Now a separate instance does not mean that each tab will only produce one thread.  Having multiple threads is not a bad thing, and actually is probably better splitting tasks to increase efficiency. 

In other words.  This is normal.


I see. Thank you for this.

Offline

Board footer

Powered by FluxBB