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.

Sign up for GitHub

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

Jump to bottom

Investigate possible memory leak from unreleased use of poco XML document and node lists. #8898

Closed
abuts opened this issue Sep 30, 2013 · 1 comment
Closed

Investigate possible memory leak from unreleased use of poco XML document and node lists. #8898

abuts opened this issue Sep 30, 2013 · 1 comment
Assignees
@KarlPalmen
Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period.
Milestone
Release 3.1

Comments

@abuts
Copy link
Member

abuts commented Sep 30, 2013

This ticket is blocks : TRAC10637

It was noticed during the work on unrelated ticket http://trac.mantidproject.org/mantid/ticket/6447, that there is possible memory leak in the Box controller code transforming BC to/from xml. This has been found not to be the case, but similar have been found elsewhere in the code.

Possible memory leaks arising from non-release of Poco::XM::document and any node list extracted from it should be investigated and fixed if identified.

Keywords: maintenance
@abuts
Copy link
Member Author

abuts commented Jun 3, 2015

This issue was originally trac ticket 8053

@abuts abuts added Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period. labels Jun 3, 2015
@abuts abuts added this to the Release 3.1 milestone Jun 3, 2015
@abuts abuts closed this as completed Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KarlPalmen KarlPalmen

Labels
Framework Issues and pull requests related to components in the Framework Maintenance Unassigned issues to be addressed in the next maintenance period.
Projects
None yet
Milestone
Release 3.1
Development

No branches or pull requests
2 participants
@abuts @KarlPalmen