The first launch after a reboot is one where the memory is less fragmented, and possibly where other tasks have not started, so clean memory access is most likely. The current manifest file reader takes in the full file at one time and breaks it apart in memory. This worked well when there was only volume information present, but the addition of the file-changed list made this operation much more memory intensive (added in 0.7.03). Forking a gpg task takes a good bit of memory and the error message sounds generic, so I'm inclined to lean towards memory issues.
To play it safe, I will change the status and leave this note that I'm sure it's related to: https://bugs.launchpad.net/bugs/1720159 ** This bug is no longer a duplicate of bug 1720159 Cannot allocate memory with large manifest file since 0.7.03 ** Changed in: duplicity (Ubuntu) Status: New => In Progress ** Changed in: duplicity (Ubuntu) Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727653 Title: duplicity fails with unknown error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1727653/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
