11GB disk space leak
-
- Posts: 630
- Joined: September 18th, 2004, 5:16 am
11GB disk space leak
I have been using seamonkey for some time. I decided to uninstall it, as it had some bug I couldn't suss out about displaying photos. Uninstall doesn't have the option to remove associated data, so then I did a search from C: for seamonkey. I found 11 GB of files named CACHE.TRASHfollowed by numbers. Good golly Miss Molly.
Last edited by karenanne on February 24th, 2017, 11:25 pm, edited 1 time in total.
- DanRaisch
- Moderator
- Posts: 127187
- Joined: September 23rd, 2004, 8:57 pm
- Location: Somewhere on the right coast
Re: 11GB memory leak
Cache files are not a memory leak. They represent data saved on the local system to speed up performance by allowing access to material previously downloaded so it doesn't have to be downloaded again.
- James
- Moderator
- Posts: 27999
- Joined: June 18th, 2003, 3:07 pm
- Location: Made in Canada
Re: 11GB memory leak
Memory leak is when a program is using lots of RAM, not hard drive space.
SeaMonkey moves the current cache folder to a cache trash folder if SeaMonkey hasn't updated the cache index files properly on the previous close down. You can remove the trash folder(s) if SeaMonkey hasn't done this automatically on a next start.
SeaMonkey moves the current cache folder to a cache trash folder if SeaMonkey hasn't updated the cache index files properly on the previous close down. You can remove the trash folder(s) if SeaMonkey hasn't done this automatically on a next start.
-
- Posts: 630
- Joined: September 18th, 2004, 5:16 am
Re: 11GB memory leak
Yeah, not a memory leak, I apparently had a personal memory leak myself
But 11GB!! What casual user like myself would even think that was happening behind the scenes.
But 11GB!! What casual user like myself would even think that was happening behind the scenes.
-
- Posts: 102
- Joined: September 3rd, 2014, 7:20 am
Re: 11GB memory leak
otherwise Facebook and Twitter are really causing memory leaks...
- JayhawksRock
- Posts: 10433
- Joined: October 24th, 2010, 8:51 am
Re: 11GB memory leak
My take > Too many live feeds on Facebook and Tweeter otta' suck up Cache.... the 300 live feeds you have are likely cached in memory.... not written to disc
"The trouble with quotes on the internet is you never know if they are genuine" ...Abraham Lincoln
-
- Posts: 630
- Joined: September 18th, 2004, 5:16 am
Re: 11GB memory leak
Or someone posts a no information reply and other people get email notices and bring up browsers, assuming it adds information.Zerebralus wrote:otherwise Facebook and Twitter are really causing memory leaks...
-
- Posts: 630
- Joined: September 18th, 2004, 5:16 am
Re: 11GB memory leak
These were written to the disk, as noted in a subsequent message. Many files, totaling GBs.JayhawksRock wrote:My take > Too many live feeds on Facebook and Tweeter otta' suck up Cache.... the 300 live feeds you have are likely cached in memory.... not written to disc
-
- Posts: 1361
- Joined: December 15th, 2015, 1:20 pm
Re: 11GB disk space leak
> CACHE.TRASH
Trash files are usually only left when something did go wrong e.g. the browser crashed or the OS crashed while the browser was open. You usually can delete them.
2.48 will switch to cache2 which is a newer api and might perform better.
FRG
Trash files are usually only left when something did go wrong e.g. the browser crashed or the OS crashed while the browser was open. You usually can delete them.
2.48 will switch to cache2 which is a newer api and might perform better.
FRG