Closed Bug 1059979 Opened 10 years ago Closed 10 years ago

"TypeError: rawLinks.map is not a function" when opening new tab page (with "A coding exception was thrown in a Promise resolution callback.")

Categories

(Firefox :: Tabbed Browser, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1059591

People

(Reporter: dholbert, Unassigned)

References

Details

STR:
 1. Start Firefox Nightly, with a fresh profile. e.g.:
      mkdir /tmp/foo3; firefox -profile /tmp/foo3 -no-remote
 2. Open a new tab.
 3. Check your terminal where you started Firefox from.

ACTUAL RESULTS: This error output in my terminal:

*************************
A coding exception was thrown in a Promise resolution callback.
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise

Full message: TypeError: rawLinks.map is not a function
Full stack: DirectoryLinksProvider_getLinks/<@resource://gre/modules/DirectoryLinksProvider.jsm:382:17
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:865:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:7

*************************


NOTE: The rawLinks.map call mentioned in the error is here:
> 377     this._readDirectoryLinksFile().then(rawLinks => {
> 378       // Reset the cache of enhanced images for this new set of links
> 379       this._enhancedLinks.clear();
> 380 
> 381       // all directory links have a frecency of DIRECTORY_FRECENCY
> 382       aCallback(rawLinks.map((link, position) => {
http://mxr.mozilla.org/mozilla-central/source/toolkit/modules/DirectoryLinksProvider.jsm?rev=d76f7a57af61#382

Adding depenency on bug 975211, which added this line of code.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
dholbert, does this happen *right now* with a fresh profile? There was an incorrectly formatted remotely hosted file yesterday for a few hours that triggered this.
Sorry -- I actually *can't* reproduce this with a fresh profile. I was using a pre-existing recently-fresh profile, which I might've created yesterday during the few hours you mentioned. (not sure)
(And I can continue to reproduce it with that broken profile. A truly fresh profile is fine, though.)
You need to log in before you can comment on or make changes to this bug.