A substantial delay is being experienced in closing idle tabs on a system using Google Chrome Version 27.0.1453.110 m on a Windows 7 x64 machine with 16GB. Chrome settings are used to launch Chrome with around 30 tabs of commonly used sites. This had been standard practice for the past 18 months or more, and previously this didn't present any problems.
Symptom Tabs that have been idle for some time (swapped out?) cannot be closed without locking up Windows 7 (freezing of cursor and keyboard) for almost 45 seconds. The Windows swap space was set to be self-managed by Windows, and was set to 16GB. More recently used tabs could be closed without difficulty. Further, even tabs that showed difficulties closing could be activated and browsed normally without latency.
Update 12 July 2013 This appeared to be caused by Windows 7 not having enough swap space. New setting shown below.
No comments:
Post a Comment