Closed Bug 1388056 Opened 7 years ago Closed 7 years ago

Sometimes new tab won't load (console shows error `addMessageListener is not defined`)

Categories

(Firefox :: New Tab Page, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1387852
Tracking Status
firefox57 --- affected

People

(Reporter: timdream, Unassigned)

Details

Happens to me on today's Nightly macOS Version 57.0a1 (2017-08-07) (64-bit)

ReferenceError: addMessageListener is not defined
[Learn More]
activity-stream.bundle.js:736:3
initStore
resource://activity-stream/data/content/activity-stream.bundle.js:736:3
<anonymous>
resource://activity-stream/data/content/activity-stream.bundle.js:2724:15
__webpack_require__
resource://activity-stream/data/content/activity-stream.bundle.js:20:12
<anonymous>
resource://activity-stream/data/content/activity-stream.bundle.js:66:18
<anonymous>
resource://activity-stream/data/content/activity-stream.bundle.js:1:11
STR:

1. Cmd+T


Expect result:

1. New tab content w/ onboarding overlay and button.

Actual result:

1. Blank page with only onboarding overlay and button.
2. Open DevTools console shows the error in comment 0.
Sounds like bug 1387852. Is this consistently on every restart? Do you have any special sessionstore or startup prefs? Or maybe addons?
(In reply to Ed Lee :Mardak from comment #2)
> Sounds like bug 1387852. Is this consistently on every restart? Do you have
> any special sessionstore or startup prefs? Or maybe addons?

I couldn't figure out how to reproduce this reliability. Let's dup given it's the same JS error.
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.