This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

YouTube isn't working with my Firefox profile - best way to fix?

  • 1 reply
  • 0 have this problem
  • 8 views
  • Last reply by zeroknight

matt218
matt218
more options

Whenever I go to youtube, it fails to work and leaves an error in the console similar to

Uncaught Error: Constructing ytd-app: [Exception... "File error: Corrupted" nsresult: "0x8052000b (NS_ERROR_FILE_CORRUPTED)" location: "JS frame :: https://www.youtube.com/s/desktop/050e6796/jsbin/desktop_polymer_enable_poly_si.vflset/desktop_polymer_enable_poly_si.js :: kCb :: line 9877" data: no]

I've determined that I can fix the problem by deleting my Firefox profile. I'd prefer to avoid this since there's a lot of useful history there. Is there a more targeted fix the problem I'm seeing?

Whenever I go to youtube, it fails to work and leaves an error in the console similar to Uncaught Error: Constructing ytd-app: [Exception... "File error: Corrupted" nsresult: "0x8052000b (NS_ERROR_FILE_CORRUPTED)" location: "JS frame :: https://www.youtube.com/s/desktop/050e6796/jsbin/desktop_polymer_enable_poly_si.vflset/desktop_polymer_enable_poly_si.js :: kCb :: line 9877" data: no] I've determined that I can fix the problem by deleting my Firefox profile. I'd prefer to avoid this since there's a lot of useful history there. Is there a more targeted fix the problem I'm seeing?

All Replies (1)

zeroknight
zeroknight
more options

Try clearing site cookies and disabling Tracking Protection for the site.

Does it still happen in Troubleshoot Mode?