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 occasional crash in PulseShapeFitOOTPileupCorrection for zero processed events in a job (as in #6646 ) #6647
fix occasional crash in PulseShapeFitOOTPileupCorrection for zero processed events in a job (as in #6646 ) #6647
Conversation
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar |
Good to see that the magic works! Have you tried to look how much RECO is affected by random memory? That is, running with different |
+1 |
fix occasional crash in PulseShapeFitOOTPileupCorrection for zero processed events in a job (as in #6646 )
That's on my to-do list On 11/27/14, 4:24 AM, davidlt wrote:
Vyacheslav (Slava) Krutelyov |
Initialized data members
the crash in e.g. 106.0 is gone.
The crash in the original code can be more reliably reproduced with the malloc magic