Jeff Morriss wrote:
Hi list,
I noticed that with 0.10.12 if I load a compressed (e.g., gzip'd) file
the file size in the progress window grows as the file is read in. I
guess it's being uncompressed on the fly now? (What would be really
cool is if that could be done in another thread so that we could take
advantage of other CPUs ;-))
I don't know about any changes regarding this. Please note that this
might be caused by a new libz version, which may have changed things
here. We have at least a new libz version in the windows version.
This has a couple of interesting side effects, though: first, the
"time left" grows as the file is loaded (which is, of course, a bit
disconcerting). Second (which I don't understand) is that when the
progress window goes away there is usually quite a bit of "time left"
(in fact the amount of "file processed" hasn't reached the "file to
read" number either).
As an example, I have a 13 Mb file that is compressed down to 3 Mb.
The "Time left" first appears as around 10 seconds but then grows to
2.5-3 minutes before the load is done.
Explanation is simple.
If you look at the file sizes in the Status row you may have noticed
that both values represent number of bytes (KB/MB). The first one should
be the currently processed value, the second one should be the "end
value" (100%). You may load an uncompressed file and have a look at how
it should be (it's working correct).
But with compressed files both values are permanently increasing.
As these "basis values" are already deeply wrong, all "derived values":
the percentage values and the progress bar simply following these wrong
values, which at whole doesn't make any real sense.
I didn't digged any deeper what's causing this, only watching what's
happening.
You may file a bugzilla about this one (don't forget to provide at least
info about your platform and libz version).
Regards, ULFL
