Closed
Bug 54724
Opened 26 years ago
Closed 26 years ago
Crash due to full cache array in AssociateCacheEntryWithRecord
Categories
(Core :: Networking: Cache, defect, P3)
Core
Networking: Cache
Tracking
()
People
(Reporter: jesup, Assigned: neeti)
References
Details
(Keywords: crash)
Attachments
(1 file)
|
31.24 KB,
text/plain
|
Details |
FreeBSD 4.1 20000928xx
I was looking at a web page pointed to by an entry in bug 48203, and I got this
assertion. After I continued from the assertion, it crashed.
It appears the problem is in nsReplacementPolicy::AssociateCacheEntryWithRecord
because it wants to extend the array (since all the entries are used), and
the calculation for the new size is:
newCapacity = mCapacityRankedEntriesArray + STATS_GROWTH_INCREMENT;
if (newCapacity > mMaxEntries)
newCapacity = mMaxEntries;
But mNumEntries is already the same as mMaxEntries, so this merely realloc's
the same size as before, so there are still no empty entries. This causes an
assertion, and also will I think cause it not to delete any entries.
I suggest either allowing them to grow beyond mMaxEntries(?), or rework things
to check for this case and instead delete an entry. The problem with that
is that this was called from DeleteAtleastOneEntry()...
Right after continuing from this assertion, mozilla segfaulted. See
backtrace of the segfault at the end of this file.
Backtrace and many structure dumps attached
| Reporter | ||
Updated•26 years ago
|
| Reporter | ||
Comment 1•26 years ago
|
||
*** This bug has been marked as a duplicate of 54072 ***
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•