Memory Leak in NSS (PK 11)

RESOLVED FIXED in 3.3.2

Status

NSS
Libraries
P1
normal
RESOLVED FIXED
16 years ago
16 years ago

People

(Reporter: Michael Hein, Assigned: Robert Relyea)

Tracking

3.3.2
Sun
Solaris

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
From bugsplat:


               malloc         [rtlib.o]
               calloc         [rtlib.o]
               PR_Calloc      [prmem.c:64]
               PORT_ZAlloc    [utilsecport.c:152]
               pk11_pbe_decode [pk11wrappk11slot.c:3352]
               PK11_ParamFromAlgid [pk11wrappk11slot.c:3510]
               PK11_PBEKeyGen [pk11wrappk11skey.c:4075]

The leak here is because the SECITEM_ZFreeItem free the Mech->data but this is
already a structure with More indirections... The salt is not freed and leaks 36
bytes every call.



------- Additional Comments From wtc  Oct-30-2001 06:56 ------- 

We don't use scopus/bugsplat for NSS bugs any more.
The NSS bug database is now bugzilla.mozilla.org.

Would you mind filing this bug at bugzilla.mozilla.org?
You'll need to go to http://bugzilla.mozilla.org/createaccount.cgi
to open a Bugzilla account for yourself first.  Then
go to http://bugzilla.mozilla.org/enter_bug.cgi to file
a bug report against NSS.

Thank you!

------- Additional Comments From mhein  Oct-30-2001 11:43 ------- 

I'll open the mozilla bug for you.

Comment 1

16 years ago
Bob, could you please take a look at this memory leak
report and determine the "severity" of this leak?
Does the PK11_PBEKeyGen function get called many times
by a typical client of NSS?
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

16 years ago
This memory leak should be evaluated for NSS 3.3.2.
Priority: -- → P1
Target Milestone: --- → 3.3.2

Updated

16 years ago
Assignee: wtc → relyea

Comment 3

16 years ago
I got more information from the bug reporter.

The memory leak is an increasing memory leak. It leaks
every time he calls the PK11_PBEKeyGen function.
(Assignee)

Comment 4

16 years ago
PBE keygen is not called very often in a 'typical' client. It is usually used to
unwrap private keys in pk12util, however I know a few people are using them to
generate fixed keys use to wrap passwords (usually to allow unattended restart).

I do have a fix for some memory leaks in the PBE code, and this one sounds
familiar, but they are on the 3.4 code base. I think the section it's in is
separable enough.
(Assignee)

Comment 5

16 years ago
A fix is checked in to NSS_3_3_BRANCH. to pk11slot.c

Comment 6

16 years ago
r=wtc. (pk11slot.c, rev. 1.14.2.3)
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.