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

Message consumption completed, rqueue related objects were not reclaimed, resulting in memory leakage #249

Open
mahuihong opened this issue Jan 1, 2025 · 2 comments

Comments

@mahuihong
Copy link

The version I am using is

com.github.sonus21
rqueue-spring-boot-starter
2.13.1-RELEASE

The following is the rqueue object information in the JVM heap memory printed using jmap after running for a period of time

image

@mahuihong
Copy link
Author

The strange thing about this issue is that the same code running on different machines may not necessarily reproduce

@sonus21
Copy link
Owner

sonus21 commented Jan 1, 2025

I don't think this issue is direcly related to Rqueue, can you also force gc and see if the count goes down. The count for all Rqueue objects is the same: 249,003. How many messages per second are you processing? Could there be a deadlock or similar issue? Additionally, can you filter out the names of all Rqueue classes involved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants