Also, the toolkit.storage.synchronous setting (mentioned in the upstreams bug report) which should be available in > rc2 is not to be found.
When do we think that fixed ubuntu packages are available?
Btw @travis.detert: I don't believe that this bug is going to fix your unusability issues you are describing. This bug only affects battery and hard drive life when trying to save power...
This bug is still evident in 3.0.1+build1+ nobinonly- 0ubuntu0. 8.04.2
Sample output when browsing around 5-6 pages:
$ strace -p `pidof firefox` -e fsync -tT
Process 17527 attached - interrupt to quit
14:52:10 fsync(37) = 0 <0.003523>
14:52:10 fsync(33) = 0 <0.000982>
14:52:10 fsync(37) = 0 <0.000466>
14:52:10 fsync(37) = 0 <0.000814>
14:52:10 fsync(33) = 0 <0.000643>
14:52:10 fsync(37) = 0 <0.000430>
14:52:45 fsync(79) = 0 <0.001523>
14:52:45 fsync(83) = 0 <0.000348>
14:52:45 fsync(124) = 0 <0.000849>
14:52:58 fsync(37) = 0 <0.002234>
14:52:58 fsync(33) = 0 <0.004564>
14:52:58 fsync(37) = 0 <0.000576>
14:53:06 fsync(37) = 0 <0.042619>
14:53:06 fsync(33) = 0 <0.002139>
14:53:06 fsync(37) = 0 <0.000348>
14:53:06 fsync(37) = 0 <0.000409>
14:53:06 fsync(33) = 0 <0.000318>
14:53:06 fsync(37) = 0 <0.000306>
14:53:06 fsync(37) = 0 <0.000376>
14:53:06 fsync(33) = 0 <0.000433>
14:53:06 fsync(37) = 0 <0.000319>
14:53:13 fsync(37) = 0 <0.003026>
14:53:13 fsync(33) = 0 <0.001112>
14:53:13 fsync(37) = 0 <0.000328>
14:53:13 fsync(37) = 0 <0.000392>
14:53:13 fsync(33) = 0 <0.000373>
14:53:13 fsync(37) = 0 <0.000250>
14:53:15 fsync(37) = 0 <0.002996>
14:53:15 fsync(33) = 0 <0.004490>
14:53:15 fsync(37) = 0 <0.000468>
Also, the toolkit. storage. synchronous setting (mentioned in the upstreams bug report) which should be available in > rc2 is not to be found.
When do we think that fixed ubuntu packages are available?
Btw @travis.detert: I don't believe that this bug is going to fix your unusability issues you are describing. This bug only affects battery and hard drive life when trying to save power...