mirror of https://github.com/gorhill/uBlock
c098eb8625
Corrpution would occur when reading back serialized data which contained multiple references to same instance of an object. The issue could manifest when reading cache storage-related data from the browser storage API, since the serializer is not used when reading from indexedDB. Private/incognito mode fall back on using browser storage API as cache storage. Off the top of my head, I think the following conditions all together could result in high likelihood of malfunction caused by improperly deserializing data at launch time: - Load from a selfie - Selfie created after uBO ran for a while - Selfie loaded from browser storage API (not the case by default) Possibly related to reports of uBO malfunctioning: https://github.com/uBlockOrigin/uBlock-issues/issues/3217#event-12686416838 |
||
|---|---|---|
| .. | ||
| _locales | ||
| css | ||
| img | ||
| js | ||
| lib | ||
| web_accessible_resources | ||
| 1p-filters.html | ||
| 3p-filters.html | ||
| about.html | ||
| advanced-settings.html | ||
| asset-viewer.html | ||
| background.html | ||
| cloud-ui.html | ||
| code-viewer.html | ||
| dashboard.html | ||
| devtools.html | ||
| document-blocked.html | ||
| dyna-rules.html | ||
| logger-ui.html | ||
| no-dashboard.html | ||
| popup-fenix.html | ||
| settings.html | ||
| support.html | ||
| whitelist.html | ||