We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
14.1.1
4.7.1
AppStore
Google Calendar
Meeting bar after a quit and restart uses about 20MB which is great.
Over days it starts growing in RAM usage, I've seen it hit gigabytes. I then need to quit and restart it.
This memory leak needs addressing.
Use meeting bar
Have it active for multiple days or weeks. Watch memory usage in Activity monitor
Memory usage should not increase by orders of magnitude. It should realistically stay under 50MB given that it starts at 20MB.
No response
The text was updated successfully, but these errors were encountered:
I can confirm, it uses 1.8GB!
4.8.0
/cc @leits
Sorry, something went wrong.
I'm seeing this as well on v4.8.1.
The memory usage starts off small and then grows over time:
Using it with Google Calendar with a single calendar.
Definitely a leak happening that being said my uptime is 104 days
leits
No branches or pull requests
macOS version
14.1.1
MeetingBar version
4.7.1
Installation source
AppStore
Calendars provider
Google Calendar
Bug description
Meeting bar after a quit and restart uses about 20MB which is great.
Over days it starts growing in RAM usage, I've seen it hit gigabytes. I then need to quit and restart it.
This memory leak needs addressing.
Reproduction steps
Use meeting bar
Have it active for multiple days or weeks. Watch memory usage in Activity monitor
Expected behavior
Memory usage should not increase by orders of magnitude. It should realistically stay under 50MB given that it starts at 20MB.
Screenshots/screen recordings
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: