nsPop3Protocol::CapaResponse calls PR_Free(0)

RESOLVED INVALID

Status

--
critical
RESOLVED INVALID
13 years ago
10 years ago

People

(Reporter: timeless, Unassigned)

Tracking

({crash})

Trunk
x86
Windows XP
crash

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
PR_Free doesn't appreciate null pointers, and half the time through this code block, it has one:

1255       if(pauseForMoreData || !line) 
1256       {
1257           m_pop3ConData->pause_for_read = PR_TRUE; /* pause */
1258           PR_Free(line);

Comment 1

13 years ago
On what platform? PR_Free is fine with PR_Free(0) afaik.

Comment 2

10 years ago
David, invalid?
Severity: normal → critical
QA Contact: networking.pop

Comment 3

10 years ago
yeah, invalid, I would say.  I don't know of any issues involving PR_Free(0), and unix free() is supposed to deal with null pointers. But if timeless has concrete knowledge of issues with PR_Free(0), I'd like to know about them.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
(Assignee)

Updated

10 years ago
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.