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

memory leak when loggerd/encoderd get out of sync #28857

Open
adeebshihadeh opened this issue Jul 10, 2023 · 6 comments · May be fixed by #33453
Open

memory leak when loggerd/encoderd get out of sync #28857

adeebshihadeh opened this issue Jul 10, 2023 · 6 comments · May be fixed by #33453
Assignees
Labels
Milestone

Comments

@adeebshihadeh
Copy link
Contributor

No description provided.

@adeebshihadeh adeebshihadeh added this to the 0.9.4 milestone Jul 10, 2023
@adeebshihadeh adeebshihadeh self-assigned this Jul 10, 2023
@adeebshihadeh
Copy link
Contributor Author

@deanlee want to look into this?

@deanlee
Copy link
Contributor

deanlee commented Jul 11, 2023

looks like we need to reset the LoggerdState when get out of sync, including clearing the old packages that are in the queue.otherwise it will cause endless recursive calls.

@deanlee
Copy link
Contributor

deanlee commented Jul 11, 2023

already submitted two PRs to address the memory leak issues:

#28873
#28697

It may require a few more PRs to improve the stability of loggerd.

@adeebshihadeh
Copy link
Contributor Author

Do we need both? What's the smallest possible fix for the current issue?

@deanlee
Copy link
Contributor

deanlee commented Jul 12, 2023

#28873 is for the current issue.

the smallest possible quick and dirty fix could be something like this :#28901

but I strongly recommend use #28873. the recursive call is buggy and dangerous. we really should refactoring loggerd instead of just keeping it working as it is.

@adeebshihadeh
Copy link
Contributor Author

I see, this is a big change to get in the upcoming release. I'll check out the fix you prefer after we ship this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment