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

Fix: address memory leak with single precision #4492

Merged
merged 2 commits into from
Jun 27, 2024
Merged

Fix: address memory leak with single precision #4492

merged 2 commits into from
Jun 27, 2024

Conversation

denghuilu
Copy link
Member

@denghuilu denghuilu commented Jun 26, 2024 •
edited
Loading

Reminder

  • Have you linked an issue with this pull request?
  • Have you added adequate unit tests and/or case tests for your pull request?
  • Have you noticed possible changes of behavior below or in the linked issue?
  • Have you explained the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi? (ignore if not applicable)

Linked Issue

Close #4411

@denghuilu denghuilu changed the title Fix memory leak with single precision Fix: address memory leak with single precision Jun 26, 2024
@mohanchen mohanchen added the Bugs Bugs that only solvable with sufficient knowledge of DFT label Jun 27, 2024
@mohanchen mohanchen merged commit 93d170d into deepmodeling:develop Jun 27, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mohanchen mohanchen mohanchen approved these changes

Assignees
No one assigned
Labels
Bugs Bugs that only solvable with sufficient knowledge of DFT
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

When performing relaxation calculations using single precision, the GPU memory usage keeps increasing
2 participants
@denghuilu @mohanchen