We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

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

  • 1 réponse
  • 0 a ce problème
  • 1 vue
  • Dernière réponse par 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?

Toutes les réponses (1)

zeroknight
zeroknight
more options

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

Does it still happen in Troubleshoot Mode?