1. General
  2. Pytania
0
Z odpowiedzią

Background processes

Jorr 11 lat temu • Ostatnio zmodyfikowane przez vladyslav volovyk 11 lat temu • 1

TO seems to hold in memory active Chrome processes even for persisted tabs that should not be open. Is this necessary, because apart from visual clarity, I really use TO to reduce memory usage of Chrome and I am unsure as to whether this really happens?


The screenshots below are from Chrome running *only* the Tabs Outliner window


Main chrome process in Task Manager:
https://dl.dropboxusercontent.com/u/12634956/Apps.png

Background processes in Task Manager:

https://dl.dropboxusercontent.com/u/12634956/Background.png


Odpowiedź

Odpowiedź
Z odpowiedzią
vladyslav volovyk 11 lat temu

TO does not hold in memory any Chrome processes for closed from it (or by Chrome itself) tabs.


You can easily see same artifacts on a Chrome without installed TO or with disabled Tabs Outliner. That's how Chrome work. 


Z odpowiedzią
vladyslav volovyk 11 lat temu

You can easily see same artifacts on a Chrome without instaled TO or with disabled Tabs Outliner. That's how Chrome work. 

Z odpowiedzią
vladyslav volovyk 11 lat temu

TO does not hold in memory any Chrome processes for closed from it or from Chrome itself tabs

You can easily see same artifacts on a Chrome without installed TO or with disabled Tabs Outliner. That's how Chrome work. 


Z odpowiedzią
vladyslav volovyk 11 lat temu

TO does not hold in memory any Chrome processes for closed from (or by Chrome itself) tabs.


You can easily see same artifacts on a Chrome without installed TO or with disabled Tabs Outliner. That's how Chrome work. 


Odpowiedź
Z odpowiedzią
vladyslav volovyk 11 lat temu

TO does not hold in memory any Chrome processes for closed from it (or by Chrome itself) tabs.


You can easily see same artifacts on a Chrome without installed TO or with disabled Tabs Outliner. That's how Chrome work. 


vladyslav volovyk 11 lat temu

Nor even it can actually.

Customer support service by UserEcho