Skip to content

fix: release memory after predict for 2.7.1 / (restored from v2.7 commit 15963b… #15342

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

Open
wants to merge 1 commit into
base: release/2.7.1
Choose a base branch
from

Conversation

Ugusu
Copy link

@Ugusu Ugusu commented May 22, 2025

fix: release memory after predict / (restored from v2.7 commit 15963b0

Not sure why, but the fix was not carried to the newer versions after 2.7. Faces OOM on v2.8.1. Added the suggested fix, the problem was solved.

Copy link

paddle-bot bot commented May 22, 2025

Thanks for your contribution!

@CLAassistant
Copy link

CLAassistant commented May 22, 2025

CLA assistant check
All committers have signed the CLA.

@Ugusu Ugusu changed the title fix: release memory after predict / (restored from v2.7 commit 15963b… fix: release memory after predict for 2.7.1 / (restored from v2.7 commit 15963b… May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants