Skip to content
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

fix: manually run garbage collector after cron job #52

Merged
merged 1 commit into from
Apr 23, 2024
Merged

Conversation

fabio-nettis
Copy link
Member

Description

This PR addresses a issue which would cause the memory usage to increase linearly over time by manually running the garbage collector after each cron job execution.

Fixes #51

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@fabio-nettis fabio-nettis added the bug Something isn't working label Apr 23, 2024
@fabio-nettis fabio-nettis merged commit 1a05b02 into main Apr 23, 2024
4 checks passed
@fabio-nettis fabio-nettis deleted the fix/memory branch April 23, 2024 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory: Linear memory increase causes crash
1 participant