nsScriptNameSpaceManager::LookupName(), use a double-byte hashtable?

VERIFIED WONTFIX

Status

()

defect
P3
normal
VERIFIED WONTFIX
20 years ago
20 years ago

People

(Reporter: bruce, Assigned: rickg)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

20 years ago
nsScriptNameSpaceManager::LookupName() does:
char* name = aName.ToNewCString();
nsGlobalNameStruct* gn = (nsGlobalNameStruct*)PL_HashTableLookup(mGlobalNames,
name);
nsCRT::free(name);

It was suggested that this might be avoided by using a double-byte string hash
function instead of PL_HashString().  This would help avoid the
allocation/deallocation of memory.
Moving all non-DOM[012], non-crash bugs to M15.
Assignee

Updated

20 years ago
Assignee: vidur → rickg
Assignee

Comment 2

20 years ago
Stealing this one from vidur to make his life easier.
Assignee

Updated

20 years ago
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX

Updated

20 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.