Issue metadata
Sign in to add a comment
|
Address bar search queries cause page crash on process-per-site process model
Reported by
sei...@live.com,
May 21 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1. Enable --process-per-site process model for chrome 2. Go to some page that isn't your default search engine, Google in my case, and search for anything 3. Tab(and any grouped tabs) will crash with "Can't open this page" error What is the expected behavior? Ideally the tab doesn't crash and I get sent to my default search engine(Google) to complete my search. What went wrong? The tab I am on, and any grouped tabs, will crash when I attempt to do a search on a page that isn't the default search engine, in my case Google. Did this work before? Yes 65 Chrome version: 66.0.3359.181 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I've tried switching the process model back to the default process-per-site-instance and this doesn't happen, so I believe it is something to do with the process-per-site process model. Hopefully this is helpful.
,
May 22 2018
Unable to reproduce the issue reported version on 66.0.3359.181 using Win 7 & 10. Attaching Screencast for reference. Steps -------- 1. Launched Chrome. 2. Enabled process-per-site and Group your tabs extension. 3. Changed default browser to yahoo. 4. Navigated to some pages. We are able to see the pages loading without crashing. @Reporter: As we are unable to reproduce the issue from our end.Let us know if we miss anything and can you please provide crash id >chrome://crashes. Thanks!
,
May 22 2018
The option you need is a process model that you enable at launch of chrome with the --process-per-site option, what you did was a flag for site-per-process which is about isolation, different option entirely as far as I can tell. I also tested with Google as the default search engine, and then searched from the address bar on a non-Google page(wikipedia or something).
,
May 22 2018
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
,
May 23 2018
As per comment#3 we have tested this issue and we are unable to reproduce the issue reported version on 66.0.3359.181 using Win 7 & 10. Steps ------ 1. Launched Chrome through command line with chrome executable path "\\chrome.exe --process-per-site" 2. Changed default browser to yahoo and navigated to some pages. Still we are not able to see the pages crashing. @Reporter: Could you please provide screencast if possible for better triaging this issue and also please provide crash ID's from chrome://crashes. Thanks!
,
May 23 2018
Here is a video, and an uploaded crash report from this video. Uploaded Crash Report ID 35bc843be443f55a (Local Crash ID: fb562260-b52a-46b0-95fc-b5a678aa817f) Crash report captured on Wednesday, May 23, 2018 at 2:11:53 PM, uploaded on Wednesday, May 23, 2018 at 2:14:29 PM
,
May 23 2018
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
,
May 24 2018
Thank you for providing information... As per comment #6 we forwarding this issue to In house Team to check the crash id and help in triaging accordingly. Thanks..!
,
May 25 2018
Tested the issue using #66.0.3359.181 on Win 10 as per the steps mentioned in original comment and could not reproduce the Crash. From the Crash I'd attached above this issue looks similar to issue 840794. Hence merging into it, please feel free to un-dupe if not the case. Thanks!!- |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sindhu.chelamcherla@chromium.org
, May 21 2018