followup on browser troubles
Jun. 6th, 2014 05:34 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Safari never crashed on that page. But yesterday I noticed it was using 99% of the CPU cycles on the computer.
As an example, after 13 hours, my AV program had only scanned 7800 files. When I closed the page, it only took 4 more hours to finish scanning the drive (over 160 thousand files)
That's a *major* slowdown.
I may return to that page when I get [better machine] up and running. Then I'll be able to let this one run on *just* that page whoile doing useful stuff on the other system.
As an example, after 13 hours, my AV program had only scanned 7800 files. When I closed the page, it only took 4 more hours to finish scanning the drive (over 160 thousand files)
That's a *major* slowdown.
I may return to that page when I get [better machine] up and running. Then I'll be able to let this one run on *just* that page whoile doing useful stuff on the other system.