Closed Bug 320941 Opened 19 years ago Closed 16 years ago

nsPop3Protocol::CapaResponse calls PR_Free(0)

Categories

(MailNews Core :: Networking: POP, defect)

Product:
MailNews Core
Component:
Networking: POP
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: timeless, Unassigned)

References

(
URL
)

Details

(Keywords: crash) 

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);
On what platform? PR_Free is fine with PR_Free(0) afaik.
David, invalid?
Severity: normal → critical
QA Contact: networking.pop
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
Closed: 16 years ago
Resolution: --- → INVALID
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.