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

Release class loader when a plugin fails to load #6030

Merged
merged 1 commit into from
Dec 14, 2021

Conversation

basil
Copy link
Member

@basil basil commented Dec 8, 2021

A minor bug I noticed while debugging some Windows test issues. When a plugin is successfully loaded, we properly release its class loader in PluginManager#stop, but we never do the same when a plugin fails to load. This is a legitimate (though minor) leak.

Proposed changelog entries

  • Fix a resource leak when a plugin fails to load.

Proposed upgrade guidelines

N/A

Submitter checklist

  • (If applicable) Jira issue is well described
  • Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • Appropriate autotests or explanation to why this change has no tests
  • For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There are at least 2 approvals for the pull request and no outstanding requests for change
  • Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • Changelog entries in the PR title and/or Proposed changelog entries are correct
  • Proper changelog labels are set so that the changelog can be generated automatically
  • If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

@basil basil added the bug For changelog: Minor bug. Will be listed after features label Dec 8, 2021
@basil
Copy link
Member Author

basil commented Dec 8, 2021

This PR was tested successfully in a passing Windows CI run in #6024.

@basil basil requested a review from a team December 9, 2021 18:02
@basil basil requested review from a team December 9, 2021 19:45
@@ -928,9 +931,10 @@ public void dynamicLoad(File arc, boolean removeExisting, @CheckForNull List<Plu
}

} catch (Exception e) {
failedPlugins.add(new FailedPlugin(sn, e));
failedPlugins.add(new FailedPlugin(p, e));
Copy link
Member

Choose a reason for hiding this comment

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

/**
* Constructor for FailedPlugin when we do not have an associated PluginWrapper
*/
public FailedPlugin(String name, Exception cause) {
this.name = name;
this.cause = cause;
this.pluginWrapper = null;
}
/**
* Constructor for FailedPlugin when we know which PluginWrapper failed
*/
public FailedPlugin(PluginWrapper pluginWrapper, Exception cause) {
this.name = pluginWrapper.getShortName();
this.cause = cause;
this.pluginWrapper = pluginWrapper;
}
FTR

@basil
Copy link
Member Author

basil commented Dec 13, 2021

This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process. Thanks!

@basil basil added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Dec 13, 2021
@timja timja merged commit 91675c5 into jenkinsci:master Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug For changelog: Minor bug. Will be listed after features ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants