MLK: nsIFileSpec from nsMsgFolder::parseURI()

VERIFIED WORKSFORME

Status

MailNews Core
Backend
P3
normal
VERIFIED WORKSFORME
18 years ago
10 years ago

People

(Reporter: Bruce Mitchener, Assigned: Scott MacGregor)

Tracking

({memory-leak})

Trunk
memory-leak

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta3-], URL)

(Reporter)

Description

18 years ago
the nsIFileSpec allocated within nsMsgFolder::parseURI() (serverPath) is leaked.
(Reporter)

Updated

18 years ago
Keywords: mlk

Comment 1

18 years ago
nominating for beta3.  I think this function gets called a lot. If I'm wrong 
about that, let me know so we can nsbeta3- it.
Keywords: nsbeta3

Comment 2

18 years ago
oof, yeah.. this gets called for each folder URI

Comment 3

18 years ago
- per mail triage
mark mail6 - will get to this if time permits
Keywords: mail6
Whiteboard: [nsbeta3-]
(Assignee)

Comment 4

18 years ago
Maybe this is an old bug or something but nsIFileSpec in that method uses a
nsCOMPtr and isn't leaked.

WFM
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 5

18 years ago
Purify was showing one of these leaked (at least one) the day I reported it (on 
Solaris).  Could something else leak that would cause this to leak as well?

Updated

15 years ago
QA Contact: lchiang → stephend
I don't see this anymore with a Windows 2000 trunk build running under Purify.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.