04-17-2021, 11:56 AM
OK, so the coincidence was a red herring. Not surprising, but a test is better than a guess.
As for running the local browser, have a look at /home/pi/.xinitrc
The last line launches the main chromium-browser process which spawns others.
Incidentally, /proc/<pid>/status contains lots of interesting info about a process. You can find the pid for the chromium-browser with 'type=renderer' by running 'ps aux|grep type=renderer'
Example:
Here the renderer process has pid=20035
On my Linux desktop and laptops, the main chromium-browser process spawns many processes of type=renderer, more than a dozen even with just a single tab, but we're getting only one in moOde. I've never bothered to figure out why the difference.
Regards,
Kent
As for running the local browser, have a look at /home/pi/.xinitrc
The last line launches the main chromium-browser process which spawns others.
Incidentally, /proc/<pid>/status contains lots of interesting info about a process. You can find the pid for the chromium-browser with 'type=renderer' by running 'ps aux|grep type=renderer'
Example:
Here the renderer process has pid=20035
Code:
pi@710LD:~ $ ps aux|grep type=renderer
pi 20035 10.1 20.4 608876 193644 ? Sl Apr07 1368:53 /usr/lib/chromium-browser/chromium-browser-v7 --type=renderer --field-trial-handle=15160034476641370332,6248687004281252584,131072 --enable-features=OverlayScrollbar --lang=en-GB --enable-auto-reload --origin-trial-disabled-features=MeasureMemory --num-raster-threads=2 --enable-main-frame-before-activation --renderer-client-id=6 --no-v8-untrusted-code-mitigations --shared-files=v8_snapshot_data:100
pi@710LD:~ $ cat /proc/20035/status
Name: chromium-browse
Umask: 0022
State: S (sleeping)
Tgid: 20035
Ngid: 0
Pid: 20035
PPid: 19979
TracerPid: 0
Uid: 1000 1000 1000 1000
Gid: 1000 1000 1000 1000
FDSize: 256
Groups: 4 20 24 27 29 44 46 60 100 105 109 997 998 999 1000
NStgid: 20035 4 1
NSpid: 20035 4 1
NSpgid: 19949 0 0
NSsid: 19906 0 0
VmPeak: 609960 kB
VmSize: 608876 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 324212 kB
VmRSS: 199268 kB
RssAnon: 44708 kB
RssFile: 83176 kB
RssShmem: 71384 kB
VmData: 172752 kB
VmStk: 132 kB
VmExe: 132528 kB
VmLib: 35304 kB
VmPTE: 782 kB
VmSwap: 0 kB
CoreDumping: 0
THP_enabled: 0
Threads: 11
SigQ: 0/6878
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001002
SigCgt: 00000001c0014a25
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 0000003fffffffff
CapAmb: 0000000000000000
NoNewPrivs: 1
Seccomp: 2
Speculation_Store_Bypass: unknown
Cpus_allowed: f
Cpus_allowed_list: 0-3
Mems_allowed: 1
Mems_allowed_list: 0
voluntary_ctxt_switches: 52212316
nonvoluntary_ctxt_switches: 73246359On my Linux desktop and laptops, the main chromium-browser process spawns many processes of type=renderer, more than a dozen even with just a single tab, but we're getting only one in moOde. I've never bothered to figure out why the difference.
Regards,
Kent
