chrome.tabs.discard do not always terminate the tabs process
Reported by
labobol...@gmail.com,
Mar 12 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. Use chrome.tabs.discard 2. Use process explorer and Chromes task manager for observation. What is the expected behavior? chrome.tabs.discard should terminate the process too when discarding the tab. What went wrong? Termination of the tabs process do not always happen and the process just hangs around doing nothing. Did this work before? No Does this work in other browsers? N/A Chrome version: 64.0.3282.167 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Left click (Browser action) - Discards all tabs. Right click (context menu) - A discard menu with some other options. It should be "Platform>Extensions" but there is no such option in the new issue wizard -> component menu. Picked the closest match "Blink>MemoryAllocator".
,
Apr 12 2018
As per comment #0, it seems to be a feature request. Hence, marking it as untriaged for further inputs from dev team. Thanks...!!
,
Apr 12 2018
No, it is a bug in my opinion. The processes of the discarded tabs should always be terminated, not just sometimes.
,
Apr 12 2018
If the process is shared with a tab that is not discarded it can be moved to a new tab, for example.
,
May 22 2018
Kentaro, can you help triage? |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by viswa.karala@chromium.org
, Mar 13 2018