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

correctly delete fetchers #947

Merged
merged 1 commit into from
Nov 22, 2018
Merged

correctly delete fetchers #947

merged 1 commit into from
Nov 22, 2018

Conversation

bridiver
Copy link
Collaborator

@bridiver bridiver commented Nov 22, 2018

fix brave/brave-browser#2213

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
    • Windows
    • macOS
    • Linux
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Request a security/privacy review as needed.
  • Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

  • enable rewards
  • claim grant
  • visit youtube video and make sure that is added to the table

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

@@ -521,7 +521,11 @@ void RewardsServiceImpl::Shutdown() {
}
}

for (const auto fetcher : fetchers_) {
delete fetcher.first;
}
fetchers_.clear();
Copy link
Contributor

Choose a reason for hiding this comment

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

is this line needed then based on the fact that you delete all fetchers in for above?

Copy link
Member

Choose a reason for hiding this comment

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

this clears out the pointers which point to invalid memory after they were deleted.

@bbondy
Copy link
Member

bbondy commented Nov 22, 2018

master: 3c2f5d9
0.58.x: c8e55c3

bbondy added a commit that referenced this pull request Nov 22, 2018
correctly delete fetchers
@NejcZdovc NejcZdovc deleted the issues/2213 branch November 22, 2018 18:06
@kjozwiak
Copy link
Member

Approved uplift to 0.57.x after deliberating with @rebron 👍

bbondy added a commit that referenced this pull request Nov 27, 2018
correctly delete fetchers
@bbondy
Copy link
Member

bbondy commented Nov 27, 2018

0.57.x: ac1c4ee

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.

Fixed memory leak with rewards service URL fetchers
4 participants