Render process unable to start when opening links from an application installed via Microsoft Store
Reported by
kristupa...@sbdigital.lt,
Dec 4
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. Install app called Slack from Microsoft Store (has to be installed from Microsoft Store) 2. Install Chromium into AppData folder (chrome.exe has to be inside AppData folder, using mini_installer.exe is simplest way) 3. Set Chromium as your default browser 4. Open Slack and login 5. Chromium has to be closed (not running) at this point 6. Open any link from Slack messages What is the expected behavior? Chromium starts as the default browser and opens the link as usual What went wrong? Chromium main process starts, displays the UI. Render processes are unable to start, leading to "crashed" tabs when you try to create new tabs. Crashed report ID: No, crash reports are not being generated How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? N/A Chrome version: 70.0.3538.110 Channel: stable OS Version: 10.0 Flash Version: 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. The issue disappears if Chromium starts with --no-sandbox flag (I inject additional arguments inside command_line.cc) 3. TargetProcess::TransferVariable() inside target_process.cc, 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. 4. Downloading and installing Slack directly from www.slack.com using the SlackInstaller.exe doesn't have this problem.
,
Dec 19
Like I mentioned in the initial post, there is no crash report. The main process is not able to write memory to the newly created render process (target_process.cc:TransferVariable() line with ::WriteProcessMemory). Because the write fails, browser considers it an error and shuts down the newly created process. The tab appears "crashed", but there is not crash report generated.
,
Dec 19
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by jmukthavaram@chromium.org
, Dec 19Labels: Needs-Feedback