[
https://issues.apache.org/jira/browse/AXIS2C-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549717
]
Senaka Fernando commented on AXIS2C-694:
----------------------------------------
Hi Shankar,
Can you please let us know how this bug could be re-produced? Is this still
around? and is it a rampart specific issue that crops up within the engine?
Only found that the hash leaks memory if we free the instance that holds the
reference to the hash, which may be the case in an inappropriate exit in a
non-blocking scenario. But, in all other contexts there doesn't seem to be any
leaks.
Regards,
Senaka
> Memory leak occurs when inserting element to hash table
> -------------------------------------------------------
>
> Key: AXIS2C-694
> URL: https://issues.apache.org/jira/browse/AXIS2C-694
> Project: Axis2-C
> Issue Type: Bug
> Components: util
> Affects Versions: Current (Nightly)
> Environment: windows
> Reporter: S.Uthaiyashankar
> Assignee: Dushshantha Chandradasa
> Fix For: 1.2.0
>
>
> If an non null element is inserted to hash table when the hash table is full,
> and the key is not available in the hash table, then memory leaks occur.
> refer the following stack trace:
> axutil_allocator_malloc_impl
> [d:\manjula\axis2\util\src\allocator.c:65]
> axutil_hash_find_entry [d:\manjula\axis2\util\src\hash.c:294]
> axutil_hash_set [d:\manjula\axis2\util\src\hash.c:362]
> rampart_set_security_processed_result
> [d:\manjula\rampart\src\util\rampart_sec_processed_result.c:41]
> rampart_shp_process_encrypted_key
> [d:\manjula\rampart\src\util\rampart_sec_header_processor.c:558]
> rampart_shp_process_message
> [d:\manjula\rampart\src\util\rampart_sec_header_processor.c:1135]
> rampart_in_handler_invoke
> [d:\manjula\rampart\src\handlers\rampart_in_handler.c:138]
> axis2_handler_invoke
> [d:\manjula\axis2\src\core\engine\handler.c:91]
> axis2_phase_invoke [d:\manjula\axis2\src\core\engine\phase.c:199]
--
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]
