Cache not showing more than 50 items
Categories
(DevTools :: Storage Inspector, defect, P2)
Tracking
(firefox97 verified)
Tracking | Status | |
---|---|---|
firefox97 | --- | verified |
People
(Reporter: imre.secodi, Assigned: jdescottes)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0
Steps to reproduce:
Cached a lots of files. Minimal nodejs project attached.
- npm i
- npm run generate
- npm run serve
- Open localhost:9090 - and open console, it should write the console, what is cached
Actual results:
- Open debugger, Storage -> Cache -> localhost -> myCache
- Only 50 element is showing
Expected results:
All the files are showing, or loading if I scroll to the bottom
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Assignee | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:Honza, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 3•3 years ago
|
||
Confirmed
Assignee | ||
Comment 4•3 years ago
|
||
Quick pointers, the issue comes in part from the getObjectsSize
method defined in the storage actor:
getObjectsSize(host, names) {
return names.length;
},
This is the default implementation used by all actor types except for indexeddb. And this method is used in getStoreObjects
... to check the number of items that should be returned (possibly? the storage actor's logic is hard to follow).
I think the if (names)
branch is only relevant for indexedDB and cache storages. However getObjectsSize doesn't really work in the same way for indexedDb and for cache. I think that we should only call getObjectsSize
for indexedDB
Assignee | ||
Comment 5•3 years ago
|
||
This is purely a storage actor bug, so I will unblock the datatable meta.
Assignee | ||
Comment 6•3 years ago
|
||
Updated•3 years ago
|
Comment 8•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Comment 9•3 years ago
|
||
I was able to reproduce this bug using an affected Nightly build (97.0a1, 20211209155024), following the STR from comment 0.
The issue is verified as fixed on 97.0, under macOS 11 and Win 10 x64.
Description
•