Webcontent Occlusion causing tabs to freeze in Google Chrome

A new feature designed to save battery life in Google Chrome called: Webcontent Occlusion has caused problems for many Terminal Server users.

On the support page and Chromium bugs, there are problems reported with the new experimental Webcontent Occlusion feature in Google Chrome. Webcontent Occlusion is pushed to Google Chrome stable on November 12, 2019.

Users working with Terminal Server in Google Chrome experienced technical problems such as blank tabs because of Webcontent Occlusion.

Webcontent Occlusion should allow Google Chrome to use less energy in tabs without having to close them.

occulsion web content google chrome

This feature reduces the resource requirements of active tabs when users place another active window over them. The behavior of the tabs then becomes similar to inactive or minimized tabs, to save battery life.

Web content Occlusion has been active for 5 months as a beta in Google Chrome 77 and Google Chrome 78, among others. According to David Bienvenu of the Google Chrome development team, no complaint about the functionality has appeared at this time.

The new functionality ensured that users who were also connected to the terminal server in Google Chrome, like other Terminal Server users, were given a blank tab.


Share this article online!
Sharing is caring! Do you care about a safer world wide web? I think you do! Help other people by sharing this information on social media. You can use the social media network buttons below.

 

 

You might find these articles useful

About The Author

Add Comment