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

Fix leak from HepPDT::HeavyIonUnknownID #25298

Merged
merged 2 commits into from Nov 24, 2018
Merged

Conversation

Dr15Jones
Copy link
Contributor

HepPDT::HeavyIonUnknownID creates a new particle in the case the HepPDT does not know of that particle by default. However, nothing deletes that particle. This code wraps HeavyIonUnknownID and does a thread safe cache of the particle in order to delete it later.

HepPDT::HeavyIonUnknownID creates a new particle in the case the
HepPDT does not know of that particle by default. However, nothing
deletes that particle. This code wraps HeavyIonUnknownID and does
a thread safe cache of the particle in order to delete it later.
@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @Dr15Jones (Chris Jones) for master.

It involves the following packages:

SimGeneral/HepPDTESSource

@cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@Dr15Jones
Copy link
Contributor Author

Please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 19, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/31747/console Started: 2018/11/20 00:28

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-25298/31747/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 5400 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3013311
  • DQMHistoTests: Total failures: 14807
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2998307
  • DQMHistoTests: Total skipped: 197
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.249 KiB( 31 files compared)
  • DQMHistoSizes: changed ( 250202.181 ): 0.249 KiB SiStrip/MechanicalView
  • Checked 134 log files, 14 edm output root files, 32 DQM output files

@Dr15Jones
Copy link
Contributor Author

@slava77 suggestions on how to find out what the RECO differences are in the comparison?

@Dr15Jones
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

Pull request #25298 was updated. @cmsbuild, @civanch, @mdhildreth can you please check and sign again.

@Dr15Jones
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 21, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/31796/console Started: 2018/11/21 22:20

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-25298/31796/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3013311
  • DQMHistoTests: Total failures: 3
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3013111
  • DQMHistoTests: Total skipped: 197
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 31 files compared)
  • Checked 134 log files, 14 edm output root files, 32 DQM output files

@civanch
Copy link
Contributor

civanch commented Nov 23, 2018

@Dr15Jones , may be I do not fully understand but my interpretation of this solution: an unknown particle is created for an event, has proper unique ptr, so deleted at the end. At the same time, there is no attempt to reuse unknown particles created in previous events.

@Dr15Jones
Copy link
Contributor Author

@civanch the particle is reused, right after the ParticleDataTable (PDT) called this class, the PDT caches the result. Since the PDT is caching, there is no need for the code I wrote to also cache.

@civanch
Copy link
Contributor

civanch commented Nov 23, 2018

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@fabiocos
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit c0a3b9a into cms-sw:master Nov 24, 2018
@Dr15Jones Dr15Jones deleted the fixLeakHepPDT branch November 28, 2018 16:06
@smuzaffar
Copy link
Contributor

@Dr15Jones , looks like new version of HepPDT has fixed the memory leak issue ( cms-sw/cmsdist#6548 (comment) ) . Should we revert this change in order to integrate HepPDT 3.04.01?

cmsbuild added a commit that referenced this pull request Jan 18, 2021
Revert #25298; memory leak fix for HepPDT::HeavyIonUnknownID
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.

None yet

5 participants