samaaron

One solution would be to set the BOOST_INTERPROCESS_SHARED_DIR_PATH to something that's in a directory only the current user can access. Would the location that the .sonic-pi directory currently resides in be a good spot for that? This might fix this issue (which we've seen flare up quite a bit as Boost uses a pretty error-prone process to determine the name of this file).

Interesting. Could you let me know the name(s) of the file(s) in that interprocess directory? Also, who is the owner? Is it the user that last logged in?

Great that this was a fix. @BOOT3988 - do you know if there's anything we could do to improve Sonic Pi's boot process to avoid this in the future? Do you know what might be causing it? Is this perhaps because other apps are using Boost's interprocess stuff - or is it somehow Boost getting confused with itself? Also, if there any other things you think we could do to improve Sonic Pi's boot stability then I'd love to hear.