462585 - etilqs_XXX file created over and over again (overwrites itself over and over again) when a website is loaded

Status: RESOLVED WONTFIX

(Core :: SQLite and Embedded Database Bindings, defect)

Description

[illya_]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

etilqs_XXX files (example: etilqs_WixrN8ruj86qymulJhDy) is created in C:\document and settings\xxxxxx\local settings\temp
and is then overwritten over and over again.
It happens most of the time a website is loaded (about 8 times per loaded webpage). It doesnt write to the file when nothing is loading.

Problem: because it is created over and over again it wears down Solid State Disks (which can only be written to a fixed amount of times before the disk dies)(Example those new eee netbooks which have a ssd instead of a harddrive).

There is also no way to move it (like you can with firefox cache) to a ramdisk.

Reproducible: Always

Steps to Reproduce:
0.Start filemon to see what firefox writes to the disk
1.Install firefox 3.0.3 cleanly, no addons or anything(or 3.0.1) (problem didnt exist with firefox 2)
2.Start firefox
3.firefox writes to the file a couple of times
4.Go to any new site
5.firefox writes to the file a couple of times again
...
Actual Results:  
I started the application, or opened a new site. And firefox writes to the file over and over again. (about 8 times per webpage)

 It DOESNT write to the file when nothing is loading.

Expected Results:  
not created it at all or, not overwrite itself over and over again. You should be able to move it to another folder (as a ramdisk) so it doesnt wear out the harddrive (or solid state driver). Or atleast stop it from writing that many times to the folder.

Comment 1

[Matthias Versen [:Matti]]

The file is from sqlite and the problem that files are created over and over again has to be solved by SSD disks and in fact they have an internal management to solve such issues and it's no problem for modern disks with internal write and defect management.
You can of course move it to another folder, move the windows temp directory to another place.

Comment 2

[Shawn Wilsher :sdwilsh]

Mitigated somewhat by bug 442967 and its dependencies, but this is WONTFIX.  SQLite has to do these writes for ACID compliance.

You can move the temp folder as suggested in comment 1.