Closed
Bug 164299
Opened 22 years ago
Closed 17 years ago
memory leaks when Viewing source
Categories
(Core Graveyard :: View Source, defect)
Tracking
(Not tracked)
People
(Reporter: Brade, Assigned: Brade)
Details
(Keywords: memory-leak)
Choosing View Source causes "definite" memory leaks in Chimera (according to
mallocDebug).
The memory is being allocated from this stack (6890 bytes in 689 nodes):
malloc
PR_Malloc
nsMemoryImpl::Alloc(unsigned long)
nsMemory::Alloc(unsigned long)
nsStrPrivate::Alloc(nsStr &, unsigned int)
nsStrPrivate::Realloc(nsStr &, unsigned int)
nsStrPrivate::EnsureCapacity(nsStr &, unsigned int)
nsStrPrivate::GrowCapacity(nsStr &, unsigned int)
nsString::SetCapacity(unsigned int)
nsString::SetLength(unsigned int)
nsAString::UncheckedAssignFromReadable(nsAString const &)
nsAString::do_AssignFromReadable(nsAString const &)
CStartToken::CStartToken(nsAString const &, nsHTMLTag)
nsTokenAllocator::CreateTokenOfType(eHTMLTokenTypes, nsHTMLTag, nsAString const &)
...
the above stack is called from both:
CViewSourceHTML::WriteTag(int, nsAString const &, int, int)
CViewSourceHTML::BuildModel(nsIParser *, nsITokenizer *, ...)
both of these are called from:
nsParser::BuildModel(void)
Comment 2•21 years ago
|
||
I don't see why this bug is Camino specific.
Add pp@lupusdesing in cc because he is cited in the nsParser.cpp.
"CViewSourceHTML::WriteTag(int, nsAString const &, int, int)" does not exits in
the above file.
Assignee | ||
Comment 3•21 years ago
|
||
changing to browser component per e-mail from Ludovic Hirlimann
<qa-mozilla@hirlimann.net>
Component: General → ViewSource
Product: Camino → Browser
Version: unspecified → 1.0 Branch
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•