Please accept my greatest gratitude for developing such a marvelous software, one that excels at crashing right when saving, while also making sure to destroy everything I had saved before. That level of brilliance is simply unmatched.
Truly, only the most genius minds could come up with a system where hours of work vanish into thin air with a single click. It’s not just buggy — it’s an act of sabotage disguised as software. Seriously, hats off, this isn’t a bug, it’s a masterpiece of frustration.
Thank you for reminding us all that progress can always be erased in an instant. Your contribution to wasted time, broken nerves, and pure rage is invaluable.
Hi @dfajtai and welcome back to the forum! It appears there is some possible corruption when loading your nrrd file. Are you able to replicate the crash consistently? If you pull the volume locally instead of on your NAS does it have the same issue? Have you modified the NRRD header in any way while it had been saved in a compressed format thereby corrupting the expected size of the file?
Yes, I tried to open it about 10 times, using various scenarios. First, I tried to reopen the scene from Recent Files. Then I tried opening the scene manually. After that, I opened the scene from an already running Slicer instance. I also tried with an older version of Slicer (the scene was initially created with version 5.6.2). Then I attempted to load only the segmentation. Finally, I moved the files to a local SSD drive and repeated the last three attempts. None of them worked.
What I truly do not understand is that until today, I thought Slicer had a quite robust and sophisticated saving procedure: initialize a temporary writer, write the actual stage to temporary files, and once completed, overwrite the old version with the new one before removing the temp files. However, in this case I ended up with neither temporary files nor the original, just the corrupted one. What exactly happened here? (Aside from the fact that I just lost 4–5 hours of work.
