I left Fusion 360 with a couple documents open last night. Tonight, I want to save them, and they each give this message:
This happens repeatedly for these files. I'm afraid to close Fusion because it may loose my work?
Exports to 3fd also fail with this message. (And one file contains embedded references and so cannot be saved as f3d ?!)
Please help!
-c
PS: Does pressing Command-C on an error message (in bottom left) really clear it instead of copying it to clipboard?!
Here's the complete error message:
Error: /Stage/BB15.9_0921_MAC/BB15.9/Protein/src/xirang/xirang/vfs/vfs.cpp(410)failed to create temp file in directory: Error: Save of document ePillMinder v3 v0 failed
Any suggestions would be appreciated.
-c
Have you tried Export and save as f3d from the File menu. It will allow you to make a local copy but you'll lose all the old versions. Unfortunately you can't make a local copy if you have external linked parts.
Mark
Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Did you run an app like CCleaner that clears junk files off your hard drive while Fusion was open?
I had what appears to be the same issue and thats what was causing it for me.
Fusion creates files in a temp directory when you start it and if you run an app that deletes those you can't save.
Not sure if this is your problem just thought I would share this info.
Phil Procario Jr.
Owner, Laser & CNC Creations
Hi,
I can confirm Phil's reply, if you are running a tool which deletes temp files while Fusion is open then it can cause these errors. In addition, if your temp folder is set to use a network drive and the connection to that network drive has been lost, then it can cause the errors.
Can you check where your temp folder is currently set and confirm that it is still accessible ? (This is usually the TMP / TEMPDIR or TEMP environment variable)
Regards,
Matt Pooley
On Behalf of the Fusion Dev Team
Just had this happen again. I'm not running Carbon Copy Cleaner or anything like that. I'm not connected to network drives. This is on Mac OS 10.11.1.
Here's the Fusion process still running on my machine:
> ps auwwxE | grep Fusion cmason 29844 0.0 0.0 2655252 876 ?? S Thu07PM 0:01.04 /Users/cmason/Library/Application Support/Autodesk/webdeploy/production/7a3b2d2378fae3fb9ca6087aa2563a5ab7a9d68f/Autodesk Fusion 360.app/Contents/Frameworks/AIRMAX/adexmtsv /Users/cmason/Library/Application Support/Autodesk/Common/Material Library/15102001/adexmtsv_prod.cfg -p /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/Neutron//15102001cmason TMPDIR=/var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/ __CF_USER_TEXT_ENCODING=0x1F6:0x0:0x0 HOME=/Users/cmason SHELL=/bin/bash Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.upsJpChhEq/Render SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.gn6ncC6IC1/Listeners PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/bin LOGNAME=cmason DISPLAY=/private/tmp/com.apple.launchd.zcsgfQHL97/org.macosforge.xquartz:0 XPC_SERVICE_NAME=0 USER=cmason XPC_FLAGS=0x0 KMP_DUPLICATE_LIB_OK=TRUE LC_ALL=en_US.UTF-8 cmason 29842 0.0 2.6 7847932 440292 ?? S Thu07PM 20:46.93 /Users/cmason/Library/Application Support/Autodesk/webdeploy/production/7a3b2d2378fae3fb9ca6087aa2563a5ab7a9d68f/Autodesk Fusion 360.app/Contents/MacOS/Autodesk Fusion 360 TMPDIR=/var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/ __CF_USER_TEXT_ENCODING=0x1F6:0x0:0x0 HOME=/Users/cmason SHELL=/bin/bash Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.upsJpChhEq/Render SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.gn6ncC6IC1/Listeners PATH=/usr/bin:/bin:/usr/sbin:/sbin LOGNAME=cmason DISPLAY=/private/tmp/com.apple.launchd.zcsgfQHL97/org.macosforge.xquartz:0 XPC_SERVICE_NAME=com.autodesk.fusion360.519392 USER=cmason XPC_FLAGS=0x1
The TMPDIR mentioned in the Fusion processes' environment does indeed exist:
ls -ld /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/ drwx------ 47 cmason staff 1598 Dec 12 22:05 /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/
however the specific subdir mentioned on the command line does not exist:
ls -ld /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/Neutron//15102001cmason ls: /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/Neutron//15102001cmason: No such file or directory
Attempting to save a F3D file locally fails with the same error:
/Stage/BB15.9_0921_MAC/BB15.9/Protein/src/xirang/xirang/vfs/vfs.cpp(410)failed to create temp file in directory:
Even if I re-create the ".../15102001cmason" directory mentioned above, the save fails.
This is really causing me to loose significant work.
-c
Hi,
The double forward slash being used in the path is potentially problematic, this looks like a path which is being constructed dynamically, so it could be something that is handled incorrectly in the Fusion code. Since this issue just started occurring again, do you have any ideas of what may have changed to trigger it ?
Regards,
Matt Pooley
On Behalf of the Fusion Dev Team
Thanks for report this.
could you please check the folder
/var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/proteinrun
if it doesn't exist, try to create it then retry the save operation.
if it exists, could you please to use 'ls -l' to get the file access right info?
this folder should be presented and have write access, and should not be removed on fly.
Hi sunjac,
I received this error again after leaving Fusion open overnight while regenerating time consuming tool paths in CAM. Document was saved successfully immediately before starting this operation (and walking away from computer). Tonight (~24hrs later), got above errors when trying to save.
Recreating the proteinrun directory does not seem to help:
cmason@fire2:~> ps auwwx | grep -i fusion cmason 40059 1.3 2.8 8118596 476692 ?? S 6:47PM 57:49.61 /Users/cmason/Library/Application Support/Autodesk/webdeploy/production/7a3b2d2378fae3fb9ca6087aa2563a5ab7a9d68f/Autodesk Fusion 360.app/Contents/MacOS/Autodesk Fusion 360 cmason 40063 0.0 0.0 2655252 7524 ?? S 6:47PM 0:01.35 /Users/cmason/Library/Application Support/Autodesk/webdeploy/production/7a3b2d2378fae3fb9ca6087aa2563a5ab7a9d68f/Autodesk Fusion 360.app/Contents/Frameworks/AIRMAX/adexmtsv /Users/cmason/Library/Application Support/Autodesk/Common/Material Library/15102001/adexmtsv_prod.cfg -p /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/Neutron//15102001cmason cmason 43325 0.0 0.0 2445076 812 s000 S+ 6:36PM 0:00.00 grep -i fusion cmason@fire2:~> ls -l /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/ total 0 drwxr-xr-x 2 cmason staff 68 Dec 18 18:36 Neutron drwxr-xr-x 2 cmason staff 68 Dec 18 18:35 TemporaryItems cmason@fire2:~> mkdir /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/proteinrun
[Retry save.]
cmason@fire2:!> ls -l !$ ls -l /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/proteinrun
[No files in this directory after retrying save.] cmason@fire2:/usr/local/src/grbl> ls -l /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/ total 0 drwxr-xr-x 2 cmason staff 68 Dec 18 18:37 Neutron drwxr-xr-x 2 cmason staff 68 Dec 18 18:35 TemporaryItems drwxr-xr-x 2 cmason staff 68 Dec 18 18:37 proteinrun
Where shown above, I tried saving the document again (twice) and got:
Error: /Stage/BB15.9_0921_MAC/BB15.9/Protein/src/xirang/xirang/vfs/vfs.cpp(410)failed to create temp file in directory: Error: Save of document Wallet Minimal 2 v35 failed Error: /Stage/BB15.9_0921_MAC/BB15.9/Protein/src/xirang/xirang/vfs/vfs.cpp(410)failed to create temp file in directory: Error: Save of document Wallet Minimal 2 v35 failed
I also looked at creation time of tmp directories:
cmason@fire2:~ ls -ld -tU /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/ drwxr-xr-x 5 cmason staff 170 Nov 6 13:47 /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/ cmason@fire2:~> ls -l -tU /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/ total 0 drwx------ 8 cmason staff 272 Dec 18 18:31 T drwxr-xr-x 6 cmason staff 204 Nov 7 06:52 0 drwx------ 13 cmason staff 442 Nov 6 13:47 C cmason@fire2:~> ls -ld -tU /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/Neutron drwxr-xr-x 3 cmason staff 102 Dec 18 18:34 /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/Neutron cmason@fire2:~> ls -l -tU /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/Neutron total 0 drwxr-xr-x 5 cmason staff 170 Dec 18 18:57 ToolbarFramework cmason@fire2:/usr/local/src/grbl> chmod a+rwx /var/folders/yb/f6cp9tzx0bz1l86xb55scd0h0000gp/T/ [Retried save, still failed.]
I'm not exactly sure what these T, O, C dirs correspond to (are they from other processes/applications?) but it does seem like the T directory that Fusion is using was recreated around the time I started using Fusion again tonight. I'm not sure what would be removing this directory, if that's indeed what happened. I don't have antivirus or any other cleanup software installed. I do have several other applications open during the same time, including: Parallels, Evernote, Messages, Safari, Chrome, iTunes. I will try this again tonight where Fusion is the only app open. I also open and shut the computer's lid several times during the day while Fusion was running in background.
I also now get a recurring message about not being able to create a Recovery file:
I've attached Diagnostic log files here.
Can you help me understand what's going on here so I can help troubleshoot more effectively? Should I expect this directory to:
a) contain files related to my open and unsaved document, while I'm using Fusion, or,
b) simply be used *during* the save process, or
c) something else?
LMK what other information I can provide. Now that I know that I basically can't successfully leave Fusion running overnight, I'm less likely to loose data, but it's unfortunate for these scenarios involving lenghty tasks.
Thanks,
-c
Hi cjmason,
Great thanks for your help.
By design, the proteinrun folder was created after Fusion launched, and it's expected to be existing during Fusion running. As we know, some customer installed some system clean tools and run it in background, it might to remove the folder unexpectedly. so if you are in the same situation, i think you can stop it as a workaround .
In our Jan release, We will move the folder to a safer place and avoid to be removed unexpectedly.
if you have more clue about this defect, welcome to let me know.
Thanks,
-j
I just googled for some possible cause, here is an answer http://superuser.com/questions/187071/in-mac-os-x-
here is the brief:
Q: In Mac OS X, how often is /tmp deleted?
A: Short answer: by default, files that aren't accessed in three days are deleted from /tmp
How long time was your Fusion running for?
We will move the proteinrun folder to a safe place in Jan release for this issue.
Sorry for your inconvenience.
Thanks,
Jackson