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

[BUG] MetadataImage leak or hold ref too long cause oom #2332

Open
lifepuzzlefun opened this issue Mar 6, 2025 · 1 comment
Open

[BUG] MetadataImage leak or hold ref too long cause oom #2332

lifepuzzlefun opened this issue Mar 6, 2025 · 1 comment
Assignees
@lifepuzzlefun
Labels
bug Something isn't working

Comments

@lifepuzzlefun
Copy link
Contributor

lifepuzzlefun commented Mar 6, 2025 •
edited
Loading

Version & Environment

1.2

What went wrong?

MetadataImage leak

Image Image

What should have happened instead?

no leak

How to reproduce the issue?

have no idea

Additional information

log missing.

only heapdump 24G if needed
@lifepuzzlefun lifepuzzlefun added the bug Something isn't working label Mar 6, 2025
@lifepuzzlefun lifepuzzlefun changed the title [BUG] MetadataImage leak cause oom [BUG] MetadataImage leak or hold ref too long cause oom Mar 6, 2025
@lifepuzzlefun
Copy link
Contributor Author

I wonder if StreamMetadataManager.fetch0 may hold one ref of Image at epoch of 29 for very long time.

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

@lifepuzzlefun lifepuzzlefun

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lifepuzzlefun