Paul B. Gallagher wrote:
Dirk Munk wrote:
David E. Ross wrote:
You are quite correct. See bug #864047 at
<https://bugzilla.mozilla.org/show_bug.cgi?id=864047>.
At the cited URL, David E. Ross writes:
While SeaMonkey deletes the general cache on termination (per my
Private Data preference), the special caches are not deleted. Thus, I
manually delete the special caches before doing a backup.
Care to explain how you do that?
And since we don't know which cache is causing the speed problems,
disabling the cache as described may not fix the problem.
I have quite a strict view on caches, page files etc. When you
*start* an application that uses a cache, that cache should be
initialized. Data in a cache belongs to a running session, there
shouldn't be old junk from previous sessions in the cache.
Better would be to clear any caches on shutdown, so they don't survive
on disk until the next program launch. All well and good to initialize
on startup, but not as good.
An application may crash, and in that case the caches still contain
data, maybe even data that caused the crash. In your proposal you rely
on the assumption that caches are clear at start up. When I was still a
programmer, I learned never to assume anything. Check and double check,
or to make sure no junk is left in caches, records, fields and so on,
always initialize.
When I was still using the glorious Windows 98, I used a setting
that would clear the page file when I closed down Windows. It made
Windows 98 quite a lot more stable!
So I would suggest that SM also initializes the local caches at
startup!
I suppose you intend the subjunctive sense here ("I propose that SM
should be made to initialize") and not the indicative sense as written
("I hypothesize that SM actually does now initialize"). If so, I agree.
That is what I mean.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
