[jira] Updated: (AXIS2C-748) Memory leak in dep_engine.c
[ https://issues.apache.org/jira/browse/AXIS2C-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damitha Kumarage updated AXIS2C-748: Fix Version/s: 1.2.0 Memory leak in dep_engine.c --- Key: AXIS2C-748 URL: https://issues.apache.org/jira/browse/AXIS2C-748 Project: Axis2-C Issue Type: Bug Components: core/deployment Environment: Ubuntu 7.04 (Feisty Fawn) Reporter: Senaka Fernando Fix For: 1.2.0 Attachments: diff.txt When we load the dep_engine, we fetch the out-fault phases and assign them to the configuration. During the fetching process a new array list is created. This contains the phases. However, before assigning it, we have duplicated the array list and assigned the duplicate. And, during the process we have not freed the initial (fetched) array list. While going through the code, I understood that a duplicate is not necessary as the fetching process already creates a duplicate. Thus, I have removed the duplicate (new_out_fault_phases) and assigned the array list that was fetched (out_fault_phases), to the configuration. This resolves the memory leak. (refer diff.txt) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2C-748) Memory leak in dep_engine.c
[ https://issues.apache.org/jira/browse/AXIS2C-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-748: --- Attachment: diff.txt Memory leak in dep_engine.c --- Key: AXIS2C-748 URL: https://issues.apache.org/jira/browse/AXIS2C-748 Project: Axis2-C Issue Type: Bug Components: core/deployment Environment: Ubuntu 7.04 (Feisty Fawn) Reporter: Senaka Fernando Attachments: diff.txt When we load the dep_engine, we fetch the out-fault phases and assign them to the configuration. During the fetching process a new array list is created. This contains the phases. However, before assigning it, we have duplicated the array list and assigned the duplicate. And, during the process we have not freed the initial (fetched) array list. While going through the code, I understood that a duplicate is not necessary as the fetching process already creates a duplicate. Thus, I have removed the duplicate (new_out_fault_phases) and assigned the array list that was fetched (out_fault_phases), to the configuration. This resolves the memory leak. (refer diff.txt) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
