Can not reopen saved mrb file

Operating system: mac os
Slicer version: 4.11
Expected behavior: open saved mrb file
Actual behavior: can not open or import the mrb file

What Slicer version did you use to save the file?
Have you saved the scene on a virtual file system (Box, Google cloud drive) or network drive (shared network drive)?

Could you copy here the error messages from the application log (menu: Help / Report a bug) after attempting to load the scene?

Could you try renaming the file to have .zip extension and unzip it?

HELLO Andras

Thanks a lot for your response. the version slices4.11, MAC OS. the problem is I can not open any saved work in mrb. format. I usually open many files at the same time before one year but now it seems not, I need to review my work on some occasion please help me on that. no error appeared but the programme did not import or reopen the mrb. files in one drive or local drive. However, the original file can open easily. I have attached a screenshot please find it.

Regards
Ashwaj

Try with latest Slicer Preview Release. It gives a detailed report about what is going wrong during scene reading.

Note that in general you cannot open a file created by a future Slicer version (Slicer-4.11 cannot open all files saved by Slicer-4.13), so if you start saving data using the latest Slicer Preview Release then you cannot switch back to the Slicer Stable Release.

Hello Andras

These are the information you need regarding not opening the mrb post-processed images,I have tried sliceser 4.11 and 4.13 they are not responded, the images processed in slicer 4.11. The only one version opened the mrb is the old version slicer 4.10 it gives only the statistic measurement without the images.

[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Session start time …: 2021-11-29 13:21:46
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Slicer version …: 4.13.0-2021-11-25 (revision 30440 / 9ecc30b) macosx-amd64 - installed release
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Operating system …: macOS / 11.6 / 20G165 / UTF-8 - 64-bit
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Memory …: 8192 MB physical, 3072 MB virtual
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - CPU …: GenuineIntel Intel(R) Core™ i5-1030NG7 CPU @ 1.10GHz, 4 cores, 8 logical processors
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - VTK configuration …: OpenGL2 rendering, Sequential threading
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Qt configuration …: version 5.15.2, with SSL, requested OpenGL 3.2 (core profile)
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Developer mode enabled …: no
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Application path …: /Applications/Slicer 3.app/Contents/MacOS
[DEBUG][Qt] 29.11.2021 13:21:46 [] (unknown:0) - Additional module paths …: (none)
[DEBUG][Python] 29.11.2021 13:21:49 [Python] (/Applications/Slicer 3.app/Contents/lib/Slicer-4.13/qt-scripted-modules/SubjectHierarchyPlugins/AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: Annotations
[DEBUG][Python] 29.11.2021 13:21:50 [Python] (/Applications/Slicer 3.app/Contents/lib/Slicer-4.13/qt-scripted-modules/SubjectHierarchyPlugins/AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentEditor
[DEBUG][Python] 29.11.2021 13:21:50 [Python] (/Applications/Slicer 3.app/Contents/lib/Slicer-4.13/qt-scripted-modules/SubjectHierarchyPlugins/AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentStatistics
[DEBUG][Qt] 29.11.2021 13:21:50 [] (unknown:0) - Switch to module: “Welcome”

It seems that you have very little virtual memory available. On macOS I think it is due to low disk space. Please free up at least a few 10GB more disk space and see if the problem is resolved.

If not then you can share an example mrb file - upload it to your dropbox, onedrive, google drive, etc. and send the link - and we can investigate if there is any problem with the file. If you don’t want to share the file publicly then you can send the link in a private message.