Comment 2 for bug 896728

I could sort of backtrace the error down to a group of rather big files (8Gib-10Gib VMs) which I excluded for testing. With this exclusion, backup works, but I am still wondering why It seems that either the python gpg bindings (implementation?) or duplicity cache the file in memory (for no reason?). Using the gpg commandline tool this has never happened to me, so IMHO we can say It isn't essential.