Frames of Workspace events and actions affect the state of the cache and are not accumulated directly in the server. Hence, you can view and manage cache occupied by frames in the embedded browser of Creo with access to the cache.

As frames can take up considerable space in the cache,you must include this space taken up by frames into the current total cache size. However, a cache occupied by frames, especially locked frames, is not cleaned up automatically when the cache size exceeds the limit set as the preference as is the regular cleanup. Cache occupied by locked frames are not automatically cleaned up because locked frames must be unlocked before they are deleted. Only cache with purged frames is automatically cleaned up. Locally cached objects associated with the purged frames are subject to cache limit management. That is, when the number of frames in the cache reaches the limit set as the preference, old frames are automatically invalidated and removed to accommodate new frames though locked frames are not removed automatically.

You can delete the workspace to delete frames and all other contents within its cache. The deletion of frames and their associated objects can take some time. It does not delete the local cache, but only invalidates the local cache before it is automatically cleaned up.