Here's the full log. You'll notice from the log's start that duplicity crashed few times. There's also a backtrace at the end of file.
The CPU usage was again very high, between 60 and 80% during file scanning and around 20% during upload but it went above 50% when the system started to hang.
The backup process arrived to 100% in about 5 mins (but the dialog still showed the buttons to cancel/continue later) but the memory usage exploded only after 8 mins. The total system memory usage after 16 mins was at 910/991Mb. Few minutes later, duplicity's own memory usage fell a bit and the swapping reduced the usage to ~ 500Mb but then suddenly the memory usage started to grow again but I closed deja-dup before the system hanged again.
All times are from the start of the backup process.
Here's the full log. You'll notice from the log's start that duplicity crashed few times. There's also a backtrace at the end of file.
The CPU usage was again very high, between 60 and 80% during file scanning and around 20% during upload but it went above 50% when the system started to hang.
The backup process arrived to 100% in about 5 mins (but the dialog still showed the buttons to cancel/continue later) but the memory usage exploded only after 8 mins. The total system memory usage after 16 mins was at 910/991Mb. Few minutes later, duplicity's own memory usage fell a bit and the swapping reduced the usage to ~ 500Mb but then suddenly the memory usage started to grow again but I closed deja-dup before the system hanged again.
All times are from the start of the backup process.