[chromium-dev] Render process not starting when sandboxed

[k***@sbdigital.lt]

Hello,

I have a very peculiar problem. It doesn't happen in the clean Chromium
version
that my product is based on, which is 68. It would seem it has something to
do
with changes in my product, but I'm really lost so I thought I would try to
get
some help here.

It goes like this:
1) Install the browser and set it as default
2) Try to open links from other programs (such as text editors, chat
programs)
3) The main browser window (UI) opens fine
4) Whenever you try to load a page in a tab, the tab appears to be
"crashed".
Browser is trying to launch a render process for the tab, but is unable.

Here are the bits that make this a headache:
1) Some of the test users are reporting this problem on Mac (same symptoms
of
crashed tabs); however I'm unable to reproduce it on a Mac
2) I'm only able to reproduce this when opening links from a chat program
"Slack"
on Windows
3) For me it only happens after the browser is installed from the
mini_instaler.
If the default browser is located in the build directory, I'm no longer
able
to reproduce this issue.

When I hardcode the browser to have a flag --no-sandbox, the issue
disappears.
My current hypothesis is that this is somehow related to permissions /
sandboxing
of the processes. However, I'm not very well versed in sandboxing of
processes
so I have no idea where to start looking.

I have narrowed down the issue why as to why the render process is unable
to be
started, and its at TargetProcess::TransferVariable(), in the line which
does
::WriteProcessMemory which returns failure. The main process seems to be
trying
to write some global variables into the newly started render process, but is
unable.

Any thoughts or ideas are highly appreciated.

[a***@chromium.org]

Hello,

You may have found a bug. Feel free to submit it to the bug tracker:
https://crbug.com/

On Monday, December 3, 2018 at 1:03:12 PM UTC+1,

Post by k***@sbdigital.lt
Hello,
I have a very peculiar problem. It doesn't happen in the clean Chromium
version
that my product is based on, which is 68. It would seem it has something
to do
with changes in my product, but I'm really lost so I thought I would try
to get
some help here.
1) Install the browser and set it as default
2) Try to open links from other programs (such as text editors, chat
programs)
3) The main browser window (UI) opens fine
4) Whenever you try to load a page in a tab, the tab appears to be
"crashed".
Browser is trying to launch a render process for the tab, but is unable.
1) Some of the test users are reporting this problem on Mac (same symptoms
of
crashed tabs); however I'm unable to reproduce it on a Mac
2) I'm only able to reproduce this when opening links from a chat program
"Slack"
on Windows
3) For me it only happens after the browser is installed from the
mini_instaler.
If the default browser is located in the build directory, I'm no longer
able
to reproduce this issue.
When I hardcode the browser to have a flag --no-sandbox, the issue
disappears.
My current hypothesis is that this is somehow related to permissions /
sandboxing
of the processes. However, I'm not very well versed in sandboxing of
processes
so I have no idea where to start looking.
I have narrowed down the issue why as to why the render process is unable
to be
started, and its at TargetProcess::TransferVariable(), in the line which
does
::WriteProcessMemory which returns failure. The main process seems to be
trying
to write some global variables into the newly started render process, but is
unable.
Any thoughts or ideas are highly appreciated.

[k***@sbdigital.lt]

Update:
This issue only seems to happen when links are opened from Slack, when it
was installed
from Microsoft Store. If Slack is installed via the regular .exe installer
downloaded from
slack.com, the issue is not present.

Post by k***@sbdigital.lt
Hello,
I have a very peculiar problem. It doesn't happen in the clean Chromium
version
that my product is based on, which is 68. It would seem it has something
to do
with changes in my product, but I'm really lost so I thought I would try
to get
some help here.
1) Install the browser and set it as default
2) Try to open links from other programs (such as text editors, chat
programs)
3) The main browser window (UI) opens fine
4) Whenever you try to load a page in a tab, the tab appears to be
"crashed".
Browser is trying to launch a render process for the tab, but is unable.
1) Some of the test users are reporting this problem on Mac (same symptoms
of
crashed tabs); however I'm unable to reproduce it on a Mac
2) I'm only able to reproduce this when opening links from a chat program
"Slack"
on Windows
3) For me it only happens after the browser is installed from the
mini_instaler.
If the default browser is located in the build directory, I'm no longer
able
to reproduce this issue.
When I hardcode the browser to have a flag --no-sandbox, the issue
disappears.
My current hypothesis is that this is somehow related to permissions /
sandboxing
of the processes. However, I'm not very well versed in sandboxing of
processes
so I have no idea where to start looking.
I have narrowed down the issue why as to why the render process is unable
to be
started, and its at TargetProcess::TransferVariable(), in the line which
does
::WriteProcessMemory which returns failure. The main process seems to be
trying
to write some global variables into the newly started render process, but is
unable.
Any thoughts or ideas are highly appreciated.

[k***@sbdigital.lt]

Another update:
The issue is also happening in multiple Chromium version builds download
from
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html
and
https://chromium.woolyss.com/
The version I tested are 68, 69, 70, 72

Post by k***@sbdigital.lt
This issue only seems to happen when links are opened from Slack, when it
was installed
from Microsoft Store. If Slack is installed via the regular .exe installer
downloaded from
slack.com, the issue is not present.

Post by k***@sbdigital.lt
Hello,
I have a very peculiar problem. It doesn't happen in the clean Chromium
version
that my product is based on, which is 68. It would seem it has something
to do
with changes in my product, but I'm really lost so I thought I would try
to get
some help here.
1) Install the browser and set it as default
2) Try to open links from other programs (such as text editors, chat
programs)
3) The main browser window (UI) opens fine
4) Whenever you try to load a page in a tab, the tab appears to be
"crashed".
Browser is trying to launch a render process for the tab, but is unable.
1) Some of the test users are reporting this problem on Mac (same
symptoms of
crashed tabs); however I'm unable to reproduce it on a Mac
2) I'm only able to reproduce this when opening links from a chat program
"Slack"
on Windows
3) For me it only happens after the browser is installed from the
mini_instaler.
If the default browser is located in the build directory, I'm no longer
able
to reproduce this issue.
When I hardcode the browser to have a flag --no-sandbox, the issue
disappears.
My current hypothesis is that this is somehow related to permissions /
sandboxing
of the processes. However, I'm not very well versed in sandboxing of
processes
so I have no idea where to start looking.
I have narrowed down the issue why as to why the render process is unable
to be
started, and its at TargetProcess::TransferVariable(), in the line which
does
::WriteProcessMemory which returns failure. The main process seems to be
trying
to write some global variables into the newly started render process, but is
unable.
Any thoughts or ideas are highly appreciated.