From 10.5.2 to 10.5.6, Safari stored the Cache.db file in a strange place (where SafeBrowsing.db is still at), rather than in ~/Library/Caches/com.apple.Safari.
With 10.5.7, it has returned to the correct location. As a result, your cache was reset upon the update. This might be why some people thought they noticed faster performance. If your cache was fragmented before (and it was), then Safari would run faster with an empty cache.
I wonder what took Apple so long to fix the problem, and what it was really about?
With 10.5.7, it has returned to the correct location. As a result, your cache was reset upon the update. This might be why some people thought they noticed faster performance. If your cache was fragmented before (and it was), then Safari would run faster with an empty cache.
I wonder what took Apple so long to fix the problem, and what it was really about?