AD - Saving to Network Drive Hangs / Times Out / Crashes

[jgarza]

AD hangs/crashes when saving to network drive. (v 2.1.1)

Steps:

1. Open AD and start a new file.
2. Save to network drive (this is OK)
3. Import image into file and save.
4. Saving bar never finishes and hangs indefinitely (have to restart and lose work)
5. Open AD again and import image again and files saves.

Files and network drives have been allowed through AntiVirus/Firewall.

[RichardMH]

Saving to network drives can be problematic. Usual work around is to save to a local drive as an intermediate step.

[NathanC]

Hi @jgarza,

I've not been able to replicate an issue with this on a network shared folder/drive by placing an linked resource which was also located on the network share (Or stored locally), this works as expected after saving again.

It may be something specific to your setup/network which has caused the issue, the developers are aware of certain issues when saving to network locations such as when access to the drive has been temporarily lost this can cause a file to fail to save, even if the network drive is re-connected thereafter. This will hopefully be improved/fixed in a future update.

As RichardMH mentioned, we generally advise opening and saving your files to a local location, and then moving the file to the network/removable storage after to prevent any file corruptions/issues with saving.

[jgarza]

Thank you. Please test with embedded image/add to bugs list for continued testing. App crash happened to me again today in AP in the exact same way it always does. 

• Opened AP
• New file
• Save file (no issues)
• Placed image (embedded) into file from network drive
• Tried saving, the app never finishes saving and crashes.
• Opened AP again and placed image, no problems

This behavior is consistent for Affinity (none of my other graphics or vid. apps have issues with network)

Thank you for the assist. 

[Birdieman]

We get the same issue all the time working in a production environment with multiple staff trying to save to a network location. Access to the file is lost, then get a message saying the program needs to close.

If access to the file is lost can you not give the option to save to a different file name rather than the program just closing down? Often the recovery version does not recover the latest version and we have lost many hours of work due to this bug. We use the workaround of saving to a local drive now but it's a lot of hassle as multiple users can be working on the same document at different stages of it's life cycle.