Closed Bug 1485295 Opened 7 years ago Closed 7 years ago

The "cache is null" error is displayed in Browser Console after dismissing top sites, top stories or highlights

Categories

(Firefox :: New Tab Page, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1437216
Tracking Status
firefox62 --- affected
firefox63 --- affected

People

(Reporter: JuliaC, Unassigned)

Details

[Affected versions]: - 63.0a1 (2018-08-21) - 62.0b19 build1 (20180820172315) [Affected platforms]: - Windows 10 x64 - Windows 7 x64 - Ubuntu 16.04 x64 - macOS 10.13.4 [Steps to reproduce]: 1. Launch Firefox (if the profile is clean, make sure you restart the browser at least once) 2. Visit some random sites in order to populate the AS sections 3. Open the Browser Console 4. Dismiss any top site (or highlight or recommended by pocket) tile [Expected result]: - The chosen tile is successfully dismissed and no errors are triggered for this action [Actual result]: - The "cache is null NewTabUtils.jsm:1694" error is displayed in Browser Console for every dismissed tile [Regression range]: - I will look for a regression range (if it's the case) as soon as possible and provide it [Additional notes]: - The error is not reproducible before the first browser restart
We've already closed this bug a couple times, the error comes from legacy code that is not being used anymore and will go away once we remove the dead code. It does not affect the current newtab page. Closing as a duplicate of previously filed bug
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.