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
Xerces Memory Leak Cleanup #19442
Xerces Memory Leak Cleanup #19442
Conversation
ianna
commented
Jun 27, 2017
- Use cms::xerces::toString instead of xercesc::XMLString::transcode. The former has a custom deleter which deallocates memory. The latter would need an explicit memory deallocation.
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @ianna (Ianna Osborne) for master. It involves the following packages: CondFormats/CTPPSReadoutObjects @ghellwig, @arunhep, @cerminar, @cmsbuild, @franzoni, @ggovi, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
assign reconstruction |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
On 6/27/17 9:39 AM, Ianna Osborne wrote:
@slava77 <https://github.com/slava77> - comparison with baseline seems
to be ok:
Hi Yana,
I see that the implementation is different compared to the last attempt
in #19041
Was that clearly buggy?
Please clarify
Thank you.
… https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_9_3_X_2017-06-26-2300+19442/20896/136.731_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2/CTPPS_TrackingStrip_sector%2045_station%20210_fr_hr_plane%2001.html
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19442 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AEdcbvnKwk7Xsbz9VlsuTj1TQoJWc04zks5sITBZgaJpZM4OGbHf>.
|
@slava77 - yes, I just fixed the memory leak by eliminating transcode. Since it would require to write a test, I did not attempt to cleanup the code now, e.g. remove extra conversions to std::string and back to char* and their comparison. It can be done as a next step. |
+1 |