Transmission uses 100% CPU when downloading any file to a encrypted home
Bug #1087071 reported by
Jonas G. Drange
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ecryptfs-utils (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
(Since https:/
Adding any torrent (.torrent/magnet) in Transmission (2.61 (13407)) on Ubuntu 12.10 (fresh install) and downloading them to /home/$USER results in Transmission using 100% CPU and the system hanging/freezing up.
Changing the download folder to /tmp/something remedies this. I am unsure whether or not /tmp is unencrypted, probably not, but there is without a doubt a all the difference in the world between /home/ and /tmp/.
In my apport report, I am running 3.6.3, but I can reproduce this with 3.2.33.
Changed in transmission (Ubuntu): | |
status: | Confirmed → New |
affects: | transmission (Ubuntu) → ubuntu |
affects: | ubuntu → ecryptfs-utils (Ubuntu) |
To post a comment you must log in.
I can confirm the same behaviour. Ubuntu 12.10, Transmission 2.61 (13407). Downloading a torrent to a location inside an encrypted home directory causes constant, massive CPU utilization - bringing the entire system almost to a halt. The problem is completely mitigated (doing the same downloads) by moving the download destination to a directory outside your encrypted home.