Logos Web Cache is rather large

Page 1 of 1 (6 items)
This post has 5 Replies | 2 Followers

Posts 1367
JimTowler | Forum Activity | Posted: Thu, Jun 25 2015 7:50 AM

Windows 7 and Logos 6.4 RC1.

While checking a few things, I was surprised to find approx. 90 GB for the whole app, and 30 GB was in WebCache.

So what's in WebCache and can I nuke it and not break anything?

Is this maybe where its keeps media if you click "Download all Media" on things like NT221?

I still have 1.2 TB free right now, so I'm not going to panic over 30 GB but it was unexpected.

Posts 2829
Don Awalt | Forum Activity | Replied: Thu, Jun 25 2015 8:54 AM

Yes, they are your video files, which can be deleted (at least I have in the past). As a little fun-fact, if you rename any of the files with an mp3 extension (make a copy of them somewhere else first), you can play then outside of Logos!

Posts 1471
Angela Murashov | Forum Activity | Replied: Thu, Jun 25 2015 8:59 AM

JimTowler:
So what's in WebCache and can I nuke it and not break anything?

The WebCache stores all the downloaded media files so then you can watch videos, play audio or see the images while the app is running offline. If you decide to delete the files then make sure to do it while the app is not running. 

We do have a case for the issue where the WebCache files keep on increasing. I’ll link this thread to it so that we will update you once it is fixed. 

Posts 1367
JimTowler | Forum Activity | Replied: Tue, Jun 30 2015 5:10 AM

Thanks for the feedback.

Posts 1471
Angela Murashov | Forum Activity | Replied: Wed, Jul 1 2015 3:08 PM

Angela Murashov:
We do have a case for the issue where the WebCache files keep on increasing. I’ll link this thread to it so that we will update you once it is fixed. 

This issue should be fixed in 6.4 SR-1.

Posts 1471
Angela Murashov | Forum Activity | Replied: Wed, Jul 1 2015 3:08 PM

Angela Murashov:
We do have a case for the issue where the WebCache files keep on increasing. I’ll link this thread to it so that we will update you once it is fixed. 

This issue should be fixed in 6.4 SR-1.

Page 1 of 1 (6 items) | RSS