[hist] prevent nullptr access with copy from default constructor#16773
Conversation
before allocating new memory, make sure we delete potentially existing one previously
Test Results 18 files 18 suites 3d 14h 24m 27s ⏱️ For more details on these failures, see this check. Results for commit ae2a9ab. ♻️ This comment has been updated with latest results. |
to avoid segviolation when calling copy-this
|
Is the failure in |
|
|
@ferdymercury à propos |
|
Agreed thks! |
|
Hi @ferdymercury, thank you for the swift fixes! |
|
We could, but there will probably be no new patch release anyway, since ROOT 6.34.00 is only a few weeks away. And we're not going to make a new patch release just for this bugfix. Given this information, could you live without a backport? I guess the only way in which it could help you is if you build your own ROOT from source from the tip of the 6.30 and 6.32 branches, without needing a patch release. But I guess this is not the case? |
|
Hi @ywkao, following up on my last comment, what would be motivation for the backports? Are you using these older ROOT version in production and this is a crucial fix? Or you're using ROOT on your laptop and if would be easy to update to 6.34 risk-free? How we proceed depends also on that |
|
Hi @guitargeek, thank you for the information. I found that the fix has been included in the latest CMSSW release so I can continue with the unit test in cms-sw/cmssw#41932 (comment). I will let you know if there is still a need of the backport after confirming with the CMS DQM experts. |
|
Hi @guitargeek, after confirming with CMS people, we would like to have TH2Poly functional in the default CMSSW. A backport to v6.30 and v6.32 will be very helpful. |
|
I understand. The backports will be merged tonight or tomorrow morning. |
|
Thank you for the help with the root backports! |
Fixes #16771