-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory consumption by extending the log file #74
Comments
Confirming this on my machine as well,
|
remove old log file #74 switch to os_log_* APIs
🫣 yikes! Just switched over all logging to use macOS's ...also, on upgrade the installer will remove the old log file, to free up that space. Doing a bit more testing, as this change touched a ton of files, but expect a new version soon! |
Updated to
Working for me. Cheers for the quick turn around mate. |
Hi, I have noticed there's a huge BlockBlock.log file in the Library folder. Above 38 GB used. Makes sense to implement a time-based rolling logs cleanup.
P.S. Thank you for an amazing BlockBlock tool !
The text was updated successfully, but these errors were encountered: