Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Multiple prefs.js files

  • 3 respostas
  • 6 têm este problema
  • 16 visualizações
  • Última resposta por soundguy585

more options

I have a re-occurring problem in some of my firefox profile folders. The profile folder creates 999 empty prefs.js files. They are all numbered a different number all the way up to 999(i.e., pref-999.js). I don't know if it is slowing down the browser. They Are All 0 bytes.

I have a re-occurring problem in some of my firefox profile folders. The profile folder creates 999 empty prefs.js files. They are all numbered a different number all the way up to 999(i.e., pref-999.js). I don't know if it is slowing down the browser. They Are All 0 bytes.

Todas as respostas (3)

more options

This happens when there is a problem with the unnumbered prefs.js file. Firefox always creates a numbered temp file and when that has finished properly then this file is renamed to prefs.js to replace the current version of this file. It is likely that some security software is blocking this file against changes if the numbered file stays.

You will have to delete all pref-##.js and prefs.js files to see if that prevents numbered file from showing up.

more options

Thank you Cor-el for your speedy response. Your explanation sure sounds plausible. I am not sure why it is only a couple of my profiles that this is happening. I have about 6 profiles for different purposes and the rest do not have this problem. I am going to check to see what these affected profiles have in common. Right off hand I know they have add-ons for watching and downloading videos. That would probably be a good place to look. Thank you

more options

Here's an update. I think I found the problem I checked the properties of the "Prefs.js" file that has data and noticed that it was set to read-only, not allowing new data to be written. I unticked the read-only box and ran that profile and Voila! it works. So far no multitudes of Prefs.js files in the folder. It would be interesting to find out how it became read-only. Possibly an add-on or extension caused it. The saga continues...