add a DBLibReset() method to help eliminate odd silo global memory issues from corrupting leak reports

[aowen87]

There are a slew of tiny allocations silo makes and hangs on to until the end of execution. These things pollute an application's leak report. They are small but can sometimes be too prolific. We should add a function applications can call to free up all this stuff and return the library to its initial pre-execution state to help facilitate eliminating leak false alarms raised by Silo.

-----------------------REDMINE MIGRATION----------------------- This ticket was migrated from Redmine. As such, not all information was able to be captured in the transition. Below is a complete record of the original redmine ticket.

Ticket number: 1357 Status: New Project: VisIt Tracker: Feature Priority: Normal Subject: add a DBLibReset() method to help eliminate odd silo global memory issues from corrupting leak reports Assigned to: - Category: - Target version: - Author: Mark Miller Start: 02/27/2013 Due date: % Done: 0% Estimated time: Created: 02/27/2013 07:47 pm Updated: Likelihood: Severity: Found in version: Impact: 3 - Medium Expected Use: 3 - Occasional OS: All Support Group: Any Description: There are a slew of tiny allocations silo makes and hangs on to until the end of execution. These things pollute an application's leak report. They are small but can sometimes be too prolific. We should add a function applications can call to free up all this stuff and return the library to its initial pre-execution state to help facilitate eliminating leak false alarms raised by Silo.

Comments: