Open hgroover opened 3 weeks ago
Any proposal to avoid this usecase ?
It definitely appears in the logfile that the C: drive is being used for temporary storage.
It looks like the provided artifact is a .7z
archive. Am I correct in understanding that this log is generated by the extracting program such as 7zip?
Is there an existing issue for this?
Problem description
This was a slightly puzzling issue I encountered installing 1.0 rc2 on Windows 10 Pro, on a Xeon machine. I had under 1gb free on my C drive before downloading the installer to the default Downloads folder (which further reduced available space on C: to around 500mb).
I selected a folder on my additional drive (F:) and extraction started up to a certain point, where it failed with an error writing some file (on two separate attempts these were different files). I rebooted before the second attempt because after two failures I could not start the installer - it complained of failing an integrity check. I also compared the sha256 hash and it matched the expected one provided in the artifact download folder.
After freeing up some gigabytes on the C drive I attempted installation again (still installing to F: where I have over 500gb free) and it succeeded. My speculation is that there is some function in un-archiving and extracting files that uses temp space, and that got exhausted in doing the full install, causing the failure.
This is not an actual defect in the installer (PEBKAC) but in retrospect it was an issue I should have thought to address. Uninstalling my two-versions-ago previous and three-versions-ago previous Freecad versions freed up quite a bit of space. Perhaps a cautionary note that the Windows default drive should also have a minimum 2gb free space (or something) would be helpful.
Failed installation (from a second attempt) attached. install-failure1.log
Full version info
Subproject(s) affected?
Other (specify in description)
Anything else?
No response
Code of Conduct