I suppose this is not really a bug, so i have not posted it in the "bug" area.
Pixinsight32 on OSX seems to check out for quite a long time while saving or restoring a project. something about the save/restore process blocks the main thread and so you get the spinning pinwheel of death, and OSX thinks that PI is 'not responding'. is there any way to prevent that? it's not fatal but you lose the updates in the process console as the project is being saved/restored.
also, during a project restore operation i was surprised to see furious disk write activity in addition to the expected reads. i can see now that what PI is doing is restoring all of the image history from the project directory to the /tmp directory. i suppose *this* falls under "wishlist" but if you made the project functionality more integral to PI then perhaps you could avoid all this copying. what i mean is that perhaps you should *have* to start a new project when you start up PI, and then you can write the image history files to the project container directory instead of to /tmp. then there's no need to save and restore the history; it's already in the project.
for a DSLR image that's undergone a masked stretch, there is A LOT of history! it took about 5 minutes to restore my project, and it probably would have been longer if /tmp and ~ were not on different disks on my mac.
i know, i know... give them a feature they have been whining for forever and all they do is complain
