While watching Logos.log file show ResourceMetadataUpdateServiceClient processing metadata updates, noted Logos Bible Software 5 memory usage growing: up to 1.60 GB then down to 1.31 GB and counting up again along with periodic replacements of Catalog index.
In previous Logos 5 session, had so many malloc errors for "pointer being freed was not allocated" that earlier part of Logos.log file was overwritten. Force Quit was done after "Exit Now" failed to close application. Logos.log file had a request time out error for ResourceViewTracking.Client.
Wondering about memory and file usage by various Logos 5 Resource Clients ?
Keep Smiling [:)]
