-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Move module event service signals to include ~Event #46713
Conversation
The per event module level service signals now happen after the edm::Event is destroyed. This allows accomodating for temporary memory use seen by the AllocMonitors.
please test |
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46713/42671 |
A new Pull Request was created by @Dr15Jones for master. It involves the following packages:
@Dr15Jones, @makortel, @smuzaffar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Size: This PR adds an extra 36KB to repository Comparison SummarySummary:
|
Comparison differences are related to #46416 |
+core |
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. @antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The per event module level service signals now happen after the edm::Event is destroyed. This allows accomodating for temporary memory use seen by the AllocMonitors.
PR validation:
Tested with an experimental AllocMonitor that noticed the destruction of temporary View related data during ~Event.