Closed
Bug 398267
Opened 18 years ago
Closed 18 years ago
Memory leak in PR_GetHostByName found in ocspclnt.
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 397487
People
(Reporter: slavomir.katuscak+mozilla, Assigned: wtc)
Details
(Keywords: memory-leak)
I wrapped current OCSP tests with dbx and checked them for memory leaks. Here
is one leak stacks related to OCSP/PKIX:
Block in use (biu):
Found 7 blocks totaling 448 bytes (11.25% of total; avg block size 64)
At time of each allocation, the call stack was:
[1] calloc() at 0xb79308a0
[2] fgetnetconfig() at 0xbc920b4e
[3] getnetlist() at 0xbc920900
[4] setnetconfig() at 0xbc91452d
[5] __rpc_getconfip() at 0xbc94806f
[6] gethostbyname_r() at 0xbc92eba2
[7] PR_GetHostByName() at line 706 in "prnetdb.c"
[8] pkix_pl_Socket_CreateByHostAndPort() at line 1613 in "pkix_pl_socket.c"
[9] pkix_HttpCertStore_FindSocketConnection() at line 1640 in "pkix_pl_httpcertstore.c"
[10] pkix_pl_HttpDefaultClient_RequestCreate() at line 1289 in "pkix_pl_httpdefaultclient.c"
[11] pkix_pl_HttpDefaultClient_RequestCreateFcn() at line 1704 in "pkix_pl_httpdefaultclient.c"
[12] fetchOcspHttpClientV1() at line 3233 in "ocsp.c"
[13] ocsp_GetEncodedOCSPResponseFromRequest() at line 3384 in "ocsp.c"
[14] ocsp_GetEncodedOCSPResponseForSingleCert() at line 3428 in "ocsp.c"
[15] ocsp_GetOCSPStatusFromNetwork() at line 4687 in "ocsp.c"
[16] CERT_CheckOCSPStatus() at line 4592 in "ocsp.c"
We had similar leak in PR_GetAddrInfoByName() (bug 397487) and finally bug was in libc. I'm setting this bug to NSPR product to check if it's not the same problem. If you find that problem is in NSS, then please set correct category.
Comment 1•18 years ago
|
||
Slavo, you might consider filing a Solaris bug against libc.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Comment 2•18 years ago
|
||
Right. With gethostbyname_r, it is more clear that NSPR or NSS
isn't responsible for this leak because unlike getaddrinfo, the
result returned by gethostbyname_r doesn't need to be freed.
You need to log in
before you can comment on or make changes to this bug.
Description
•