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

why high number of disk writes to prefs-1.js?

  • 4 replies
  • 2 have this problem
  • 7 views
  • Last reply by proj964

more options

in windows %APPDATA%\roaming\mozilla\firefox\profiles\b6tk5rjg.default\prefs-1.ps exhibits a high number of writes using capture data from sysinternals procmon.exe on windows 7 with firefox 41.0.1. by "high", 1/3 of the total number of disk writes during the capture period. my first impression is that this is kind of hard on SSDs and tends to waste system performance.

in windows %APPDATA%\roaming\mozilla\firefox\profiles\b6tk5rjg.default\prefs-1.ps exhibits a high number of writes using capture data from sysinternals procmon.exe on windows 7 with firefox 41.0.1. by "high", 1/3 of the total number of disk writes during the capture period. my first impression is that this is kind of hard on SSDs and tends to waste system performance.

All Replies (4)

more options

You shouldn't have a prefs-1.js file. The normal preferences file name is prefs.js without the -1. You may have a security program or anti-malware application installed on that PC which prevented Firefox from writing to the prefs.js file and the prefs-1.js file was created when Firefox created a new prefs.js file for Firefox to write data into.

You may want to check with Sysinternals to find out why it is writing to that file. http://forum.sysinternals.com/

more options

hi thanks. the interesting thing I discovered is that prefs-1.js is not on the hard drive. so I posted a question in the sysinternals forum that you referenced. we'll see where this leads. right now, I am just more confused by the procmon capture data.

more options

Firefox first creates a numbered temp file with the first available number when a new file needs to be created. Once Firefox has finished with creating the file and writing all data to disk and no error has occurred then the original file in this case prefs.js is removed and the temp file is renamed to replace the prefs.js file. This protects against the case where Firefox isn't able to finish this action what would leave you with a corrupted prefs.js file that could possibly make Firefox crash.

more options

cor-el: thanks, that explains the capture of disk ops to prefs-1.js.