Closed Bug 3670 Opened 26 years ago Closed 26 years ago

Incorrect use of PL_Hash

Categories

(Core :: XPCOM, defect, P1)

All
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dp, Assigned: dp)

Details

After talking to chris waterson, I just figured out that for PL_Hash, I need to keep the strings that I use as the key around. I am not doing that. My Problem... dp Suresh Duddi wrote: I am using PL_Hash to maintain a has table keyed by strings (filenames). Here is what I find: Get(y:/moz/mozilla/dist/WIN32_D.OBJ/bin/components/ucvlatin.dll) FAILED. Get(Y:/moz/mozilla/dist/WIN32_D.OBJ/bin/components/ucvlatin.dll) FAILED. Put(Y:/moz/mozilla/dist/WIN32_D.OBJ/bin/components/ucvlatin.dll) succeeded. Get(Y:/moz/mozilla/dist/WIN32_D.OBJ/bin/components/ucvlatin.dll) succeeded. Get(Y:/moz/mozilla/dist/WIN32_D.OBJ/bin/components/ucvlatin.dll) succeeded. <bunch of other Gets and Puts> Get(Y:/moz/mozilla/dist/WIN32_D.OBJ/bin/components/ucvlatin.dll) FAILED. Put(Y:/moz/mozilla/dist/WIN32_D.OBJ/bin/components/ucvlatin.dll) succeeded. The source file that does the hashing is pretty simple: mozilla/xpcom/src/xcDllStore.cpp I am perplexed at how after some use, suddenly HashTableLookups() would start failing. Am I doing something wrong ? dp
Severity: critical → major
Priority: P3 → P1
Target Milestone: M3
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Using nsHashtable
SCC, can you mark this VERIFIED-FIXED after regressing it?
Status: RESOLVED → VERIFIED
Regressed. All ok.
You need to log in before you can comment on or make changes to this bug.