Mozilla Firefox

I've got a Kingston 96 GB SSD that I've been using since June 2011 for my C: drive. It's still plugging along, but when it dies, I'll buy a new (bigger) one and hopefully install my latest IFW image on it. I'll probably have to ask Brian K for help though.

 

I've been running the same SSD for my OS for over 6 years and have Firefox constantly open and it is still healthy.

 

Cloudcroft,

If you have an Entire Drive image of the old SSD, it's easy. Swap SSDs, restore your image and select this option...

Scale to Fit

(Those partitions smaller than 15 GB will not be expanded. Only larger ones.)




If you have partition backups rather than an Entire Drive backup it's slightly more complicated. Let's discuss the most confusing restore. A UEFI system with multiple partitions on the SSD. You have an image for each partition. Your SSD dies and you replace it with a larger SSD.

Set the Disk Type to GPT
This creates a MSR so you don't have to restore your MSR image
Restore the EFI System partition
Restore each partition in turn but keep the OS for last
Use the Update Boot partition option for each of these restores (the Boot Partition is the EFI System partition)
Now for the final OS partition restore. In addition to using Update Boot partition, put a number in the Resize after Restore box so the partition fills the drive

Done. Note, the partitions we're restored in the original order. That doesn't matter at all because you have chosen "Update Boot partition".

 

How do you do that? If you use diskpart, it doesn´t create the MSR automatically. If an MSR image is not available, it can be created manually in the "right" place, after restoring the ESP (create partition msr size=128 ).

 

Robin,

Boot IFL, click Partition Work, Change Disk Type, GPT, Yes.

In TBWinRE/PE it is Scripts, Change Disk Type, Convert a Physical drive, HD0, Conversion of disk HD0 to GPT type, Enter, Enter.

In both cases a 128 MB MSR will be created.

 

Thanks, Brian....I make Entire Drive images, so hopefully it will be simpler for me.

 

I didn't completely understand it. Isn't FF only supposed to write to disk when it loads web-pages? When does this extra write activity takes place?

 

It's all mentioned in the article:

"The default is "15000" which is 15 seconds", ... even if the system is idle these files are saved every 15 seconds. This can lead to these big write operations.

 

@ Mood

Yes I did read it, but I don't have the impression that FF writes to disk when it's idle. Or perhaps it does this so quickly that it's not noticeable. I wonder if there's some app that can monitor the total amount of data that a browser (or other app) writes to disk.

 

I checked it myself and the file is only updated if there was some "activity" (new tab or website was opened).
Not directly after each activity, but it depends on the setting mentioned in the article.
With only some opened tabs and little surfing the file is only "some KB" small. But it keeps growing.

Process Hacker, Process Monitor,...
Maybe the Windows Task manager can do it too, but i'm not sure
Or monitor the file with "Everything", and you 'll see that it is updated and it grows with each clicked link in the browser.
Edit: In the article there is a link to "ServeTheHome" with some screenshots of the Disk Activity from Firefox ("recovery.js" / "cookies.sqlite")

 

OK thanks, will check it out. I also read that some people say it shouldn't be a big issue on top quality SSD's. But of course I did change the setting.

 

Do not take this article very seriously, because its content is false, if to say softly.
There are all tangled, are two different things - these are the "cache files and cache storing" and the "recover site" function.
This very misleading story.
http://news.softpedia.com/news/adju...firefox-wears-off-your-ssd-drive-508665.shtml
---------------------------------------------
If You really do not want to store cache files on the hard disk, You may select another place for it - for example USB stick, or You may disable cache storage at all, if it is so important.
But remember, all browsers do the same, every time, if You delete something, happens the same, ie Your fils will be stored on hard drive and You can recover them later. The same happens always if You overwrite something, if You update some program etc. So, for example, any antivirus load updates itself every hour and the update files may be many megabites, because they download full package, but not only one rule. Etc.

 

It's not about the cache in the article, but especially about "recovery.js" and "cookies.sqlite" that are generating a lot of disk writes (with the default setting of browser.sessionstore.interval).
If you click the first link in the article that leads to "ServeTheHome", you'll see some screenshots about the disk activity from Firefox.
These two specific files alone generated 1.1GB disk writes within 45 minutes.

Sure, the cache generates disk writes too but it plays no role in both articles.

 

OK. You can live then with this knowledge, that is so, but may still check whether really is so. It is so simple. but always is not everything true, what is written somewhere.
All, that glitters, is not always gold.

 

What happens if we do "chattr +i recovery.js" and cookie.sqlite?

 

I cannot get firefox to play IHeart radio since the update to version 49.
i have updated flash still no luck and IHeart plays in every other browser on my computer, i'm running windows 10 AU
is there a setting i'm missing? if someone could help that would be great.
Thanks

 

Thanks for replying. I have the DRM box ticked tried unticking still no go
It will not work on two computers in my house maybe its a firewall thing?
if I figure it out i'll post the answer.

 

JR, what sites do you need to allow in NoScript?

Thanks.

 

Thanks JR, but I meant specifically to get iHeartRadio to play.

 

OK, I've just made that change in NoScript but iHeartRadio isn't playing in Cyberfox 49. I do have ABP installed but I see you didn't make any changes with it.

Edit: Even after disabling ABP it will not play.

 

Thanks for all the help, still no luck for me yet.