Issue metadata
Sign in to add a comment
|
PIA extension + one incognito tab + search + control-W causes complete browser crash
Reported by
wilderc...@gmail.com,
Dec 23
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 11151.59.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.94 Safari/537.36 Platform: 11151.59.0 (Official Build) stable-channel caroline Steps to reproduce the problem: 1. A single browser extension is enabled: PIA (details below). This extension is however not in active use because it is not configured with any login credentials. (Other extensions are installed but all set as disabled.) 2. Starting with all windows closed, invoke a single incognito browser tab by hitting control-shift-N. 3. Into the search/address box enter a small search string, e.g., “ssh”, then hit Enter. 4. After you see the search results, hit control-W. This will predictably trigger the browser crash, leading to the “Chrome didn't shut down properly” prompt. 5. The crash occurs only when a solo incognito tab is closed. If N incognito tabs are present, closing N–1 of them each with control-W does not cause the crash. The crash will occur when the last one is closed with control-W. What is the expected behavior? What went wrong? Browser crash. Crashed report ID: c68bea91881d8f29 How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes Some weeks ago. Chrome version: 71.0.3578.94 Channel: beta OS Version: 11151.59.0 Flash Version: If the PIA browser extension is not enabled, no crash occurs. If other browser extensions are also enabled, that does not affect this crash in any way. The PIA aka Private Internet Access browser extension was installed from the official Chrome Web Store: https://chrome.google.com/webstore/detail/private-internet-access/jplnlifepflhkbkgonidnobkakhmpnmh The developer of the PIA browser extension (with whom I have no connection) has offered the Chrome OS developers a test account if needed while filing a different bug report, see Issue 915835 . The following crash ids correspond to this bug. 6b431c825b5c9769 3ff94e5ba5199c5d 61fa00965437f366 99735d99df80538e 33ea797b2399425d d7486b43d3cdfb58 c68bea91881d8f29
,
Jan 14
Thank you for reporting. I have requested access to the extension to check the issue.
,
Jan 17
(5 days ago)
I could not reproduce the error. I installed PIA 1.8.1 on Chrome 71.0.3578.94 and went through the following steps, both with extensional enabled in incognito and not enabled: 1- Closed all windows. 2- Hit Ctrl+Shit+N. 3- Entered ssh in omnibox and hit enter. 4- Hit Ctrl+W. And chrome closed smoothly. Can you provide any more comments? or anything that can help reproducing the issue? I also tried a simulator and it also did not crash.
,
Jan 17
(5 days ago)
As you can tell from the crash ids in my original posting, debugging information should have already been sent to the Chrome OS developers. I am providing a little additional information below. If you need more details not already included in the debugging information automatically submitted as above, please advise me as to how best to collect and provide them to you. 1. I was unable to cause the stand-alone Chrome browser to crash in a desktop Linux environment. I observe the reported crash only Chrome OS devices. 2. For testing, I logged into my devices using a different Google account B that has never installed any Chrome extensions. I added only the PIA extension. And I was unable to cause the crash to occur. But when I log in with the Google account A that I usually use, the crash occurs predictably. So there is something in my own environment in account A that is a factor in the crash. I have a lot of apps and extensions installed in account A. To reproduce the crash I went to the Extensions screen in account A and disabled all extensions until I found the one extension (i.e., PIA) that must be enabled for the crash to occur. Can it be that the disabled extensions, or the apps (none of which is actively in use) somehow contribute to the crash? 3. While logged in with account A, I am able to cause this crash exactly in the same manner on the following devices. Each one is in developer mode. 3.1. On the "caroline" device already specified in my original issue report. 3.2. On the following "guado" device. Crash occurs as reported before today's OS update: Version 70.0.3538.110 (Official Build) (64-bit) Platform 11021.81.0 (Official Build) stable-channel guado Crash occurs as reported after today's OS update: Version 71.0.3578.127 (Official Build) (64-bit) Platform 11151.113.0 (Official Build) stable-channel guado 3.3. On the following "ninja" device. Crash occurs as reported before today's OS update: Version 71.0.3578.94 (Official Build) (64-bit) Platform 11151.59.0 (Official Build) stable-channel ninja Crash occurs as reported after today's OS update: Version 71.0.3578.127 (Official Build) (64-bit) Platform 11151.113.0 (Official Build) stable-channel ninja
,
Jan 17
(5 days ago)
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
,
Jan 17
(5 days ago)
Also, please note: The PIA extension is currently at version 1.8.1, and the crashes reported in items 3.2 and 3.3 above occurred with this version 1.8.1. So presumably the exact version of the PIA extension is not a factor.
,
Jan 18
(4 days ago)
Thank you very much, I could FINALLY reproduce it. It seems that the key point was being in developer mode. I will merge this with the bug on this issue and you can follow up there. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by wilderc...@gmail.com
, Dec 23