Bug 734760

Summary: [PEM] pem_CreateObject() leaks memory given a non-existing file name
Product: [Fedora] Fedora Reporter: Kamil Dudka <kdudka>
Component: nssAssignee: Elio Maldonado Batiz <emaldona>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: emaldona, kdudka, kengert
Target Milestone: ---Keywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: A PEM module internal function did not clean up memory when detecting a non-existent file name. Consequence: This caused memory leakage on client code. Fix: Deallocate such temporary objects. Result: The reported memory leakage is gone.
 Story Points: ---
Clone Of:
: 746632 (view as bug list) Environment:
Last Closed: 2012-03-20 20:26:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 733657, 746629, 746632, 806058    
Attachments:
Description Flags
proposed fix emaldona: review+

Description Kamil Dudka 2011-08-31 11:21:38 UTC 
Version-Release number of selected component (if applicable):
nss-3.12.11-1.fc17


Additional info:
Same bug in RHEL-6 and stable Fedora.
Comment 1 Kamil Dudka 2011-08-31 11:23:59 UTC 
Created attachment 520796 [details]
proposed fix
Comment 2 Kai Engert (:kaie) (inactive account) 2012-03-20 20:26:45 UTC 
I see this patch file is already contained in rawhide.

Marking fixed.
Comment 3 Elio Maldonado Batiz 2012-04-25 22:43:58 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: A PEM module internal function did not clean up memory when detecting a non-existent file name.
Consequence: This caused memory leakage on client code.
Fix: Deallocate such temporary objects.
Result: The reported memory leakage is gone.