This problem seems to keep coming and going. And it only has been reported on
Windows, and it seems only on some Windows machines which are configured in a
particular way (we don't know the exact criteria).
Maybe "SHOW ALL" gives some info. I would especially be interersted in the amount of free space on the tempdrive and the temporary file size generated.
Maybe there is an issue with the max file size of 2 GB
Windows is rather difficult to debug - the only way is to keep producing test
versions to spit out diagnostic messages. This is compounded by the fact that
few of the developers have or know how to use Windows. Harry is the only person
who has the skills to produce windows binaries.
Well... the only one who took the time.....
So if we are going to fix this problem we'll need a commitment from myself or
Ben (to work on the diagnosis and fix), from Harry (to build diagnostic versions)
and from Henry (to try out these diagnostic versions and report the results).
I know that people have a lot of other things to do. So the question is: Are
all those people prepared to invest the time and effort to fix this bug once
and for all?
I am willing to do it. I can't guarantee it for every single day, but normally I would be able to generate at least a build every day if the updates are available as patch to a known tarball or as tarball.
Have fun