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 occasional crash in PulseShapeFitOOTPileupCorrection for zero processed events in a job (as in #6646 ) #6647

Merged
merged 2 commits into from Nov 27, 2014

Conversation

slava77
Copy link
Contributor

@slava77 slava77 commented Nov 26, 2014

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

export MALLOC_CHECK_=3 
export MALLOC_PERTURB_=$(($RANDOM % 255 + 1))
cmsRunGlibC config.py

@slava77
Copy link
Contributor Author

slava77 commented Nov 26, 2014

+1

for #6647 cce5d3a
same as #6646

@cmsbuild
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

@davidlt
Copy link
Contributor

davidlt commented Nov 27, 2014

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 MALLOC_PERTURB_ each time and comparing the results.

@davidlange6
Copy link
Contributor

+1

@slava77
Copy link
Contributor Author

slava77 commented Nov 27, 2014

That's on my to-do list

On 11/27/14, 4:24 AM, davidlt wrote:

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
|MALLOC_PERTURB_| each time and comparing the results.


Reply to this email directly or view it on GitHub
#6647 (comment).


Vyacheslav (Slava) Krutelyov
TAMU: Physics Dept Texas A&M MS4242, College Station, TX 77843-4242
CERN: 42-R-027
AIM/Skype: siava16 googleTalk: slava77@gmail.com
(630) 291-5128 Cell (US) +41 76 275 7116 Cell (CERN)


@slava77 slava77 mentioned this pull request Dec 7, 2014
lihux25 added a commit to lihux25/cmssw that referenced this pull request Dec 7, 2014
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