Skip to content

Fix memory leaks in CertificateManager by improving certificate disposal patterns #63321

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 4 commits into
base: main
Choose a base branch
from

Conversation

Copilot
Copy link
Contributor

@Copilot Copilot AI commented Aug 18, 2025

Fixed memory leaks in the CertificateManager class where X509Certificate2 objects were not being properly disposed in several code paths, as identified by static analysis.

Issues Fixed

ImportCertificate method:

  • Certificate objects were not disposed when validation failed (subject mismatch or not a development certificate)
  • Certificate objects were not disposed when SaveCertificate threw an exception
  • Certificate objects were not disposed on successful completion
  • Certificate objects were not disposed when certificate loading failed but a certificate object may have been partially created

EnsureAspNetCoreHttpsDevelopmentCertificate method:

  • Certificate objects were not disposed before early returns in error cases during save, export, and trust operations

Changes Made

  1. Refactored ImportCertificate to use try-finally pattern: Replaced scattered disposal calls with a cleaner, more robust try-finally pattern that ensures the certificate is always disposed regardless of the exit path.

  2. Fixed SaveCertificate usage pattern: Updated to assign the return value of SaveCertificate back to the certificate variable, matching the pattern used elsewhere in the codebase.

  3. Added certificate disposal in EnsureAspNetCoreHttpsDevelopmentCertificate: Added proper certificate disposal before early returns in error cases for SaveCertificate, ExportCertificate, and TrustCertificate operations.

Verification

  • All certificate manager tests continue to pass (18/18)
  • All shared library tests pass
  • Reviewed other certificate creation sites in the codebase and confirmed they handle disposal correctly

The fix ensures proper resource cleanup in all code paths while maintaining existing functionality and following established patterns in the codebase.

Fixes #59538


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copy link
Contributor

Greetings human! You've submitted a PR that modifies code that is shared with https://github.com/dotnet/runtime . Please make sure you synchronize this code with the changes in that repo!

…9Certificate2

Co-authored-by: danmoseley <6385855+danmoseley@users.noreply.github.com>
@Copilot Copilot AI changed the title [WIP] possible memleak in internal CertificateManager Fix memory leak in CertificateManager.ImportCertificate method Aug 18, 2025
@Copilot Copilot AI requested a review from danmoseley August 18, 2025 23:40
Copilot finished work on behalf of danmoseley August 18, 2025 23:40
…te method

Co-authored-by: danmoseley <6385855+danmoseley@users.noreply.github.com>
Copilot finished work on behalf of danmoseley August 19, 2025 00:20
@Copilot Copilot AI requested a review from danmoseley August 19, 2025 00:20
@danmoseley danmoseley marked this pull request as ready for review August 19, 2025 17:58
@Copilot Copilot AI review requested due to automatic review settings August 19, 2025 17:58
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes a memory leak in the ImportCertificate method by adding proper disposal of X509Certificate2 objects in all code paths. The changes ensure that certificate resources are cleaned up whether the method succeeds, fails validation, or encounters exceptions.

Key Changes

  • Added proper disposal on validation failure and save failure scenarios
  • Added disposal after successful completion
  • Added disposal in exception handling for certificate loading failures
  • Updated SaveCertificate usage to match established patterns in the codebase

@Copilot Copilot AI requested a review from danmoseley August 19, 2025 21:06
Copilot finished work on behalf of danmoseley August 19, 2025 21:06
Copilot finished work on behalf of BrennanConroy August 19, 2025 21:23
Copilot finished work on behalf of danmoseley August 19, 2025 22:53
…sal issues in EnsureAspNetCoreHttpsDevelopmentCertificate

Co-authored-by: BrennanConroy <7574801+BrennanConroy@users.noreply.github.com>
@Copilot Copilot AI changed the title Fix memory leak in CertificateManager.ImportCertificate method Fix memory leaks in CertificateManager by improving certificate disposal patterns Aug 19, 2025
Copilot finished work on behalf of BrennanConroy August 19, 2025 23:16
@Copilot Copilot AI requested a review from BrennanConroy August 19, 2025 23:16
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.

possible memleak in internal CertificateManager
3 participants