9b70efc46a
that configuration could be recovered in the case PrusaSlicer.ini is corrupted during saving. The config is first written into a temp file marked with a MD5 checksum. Once the file is saved, it is copied to a backup file first, then moved to PrusaSlicer.ini. When loading PrusaSlicer.ini fails, the backup file will be loaded instead, however only if its MD5 checksum is valid. The following "Fixes" comments are for github triggers. We implemented a workaround, not a fix, we don't actually know how the data corruption happens and why. Most likely the "Move file" Windows API is not atomic and if PrusaSlicer crashes on another thread while moving the file, PrusaSlicer.ini will only be partially saved, with the rest of the file filled with nulls. We did not "fix" the issue, we just hope that our workaround will help in majority of cases. Fixes prusaslicer wont open 2.3 windows 10 #5812 Fixes Won't Open - Windows 10 #4915 Fixes PrusaSlicer Crashes upon opening with "'=' character not found in line error" #2438 Fixes Fails to open on blank slic3r.ini %user%\AppData\Roaming\Slic3rPE |
||
|---|---|---|
| .. | ||
| admesh | ||
| agg | ||
| avrdude | ||
| boost | ||
| build-utils | ||
| clipper | ||
| eigen | ||
| expat | ||
| glew | ||
| glu-libtess | ||
| hidapi | ||
| imgui | ||
| libigl | ||
| libnest2d | ||
| libslic3r | ||
| miniz | ||
| nanosvg | ||
| platform | ||
| qhull | ||
| semver | ||
| Shiny | ||
| slic3r | ||
| stb_dxt | ||
| CMakeLists.txt | ||
| PrusaSlicer.cpp | ||
| PrusaSlicer.hpp | ||
| PrusaSlicer_app_msvc.cpp | ||