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.

Sign up for GitHub

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

Jump to bottom

Memory leak with logging enabled #73

Open
comnik opened this issue May 5, 2019 · 1 comment
Open

Memory leak with logging enabled #73

comnik opened this issue May 5, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@comnik
Copy link
Owner

comnik commented May 5, 2019

With --enable-logging the server struct holds on to EventLink's for Timely and Differential events, resulting in those never dropping elements.
@comnik comnik added the bug Something isn't working label May 5, 2019
@comnik
Copy link
Owner Author

comnik commented May 5, 2019

Solution would be to undo my previous laziness and change SourcingContext to be a trait implemented by Server, that can hand out the event link only to a source that actually wants to make use of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@comnik