Yes, i've had this happen one in awhile. The author is constantly fixing the program and the latest 1.01 version seems better in this regard with throttleing and recovery to avoid overloading but i have not stress tested since 1.01 other than a 350mb dl which completed uninterrupted. If you still encounter issues you might experiment with setting peer or bandwith limits.

---

Just a note on two minor changes i made starting with new rev19 build. I will continue to put in later revisions so you don't need to get this unless you really want these features below :

First, i shifted open dialog a little to give another line of directory scrolling in that cramped open dlg.

Second, I created environment variable for cache relocation called TRANS_CACHEDIR which lets you move the cache dir onto an mmc.

The idea behind cache relocation is to minimize writes to internal (nonreplacable flash memory), but in practice transmission is not doing very much writing at all to the cache dir... seems maybe twice per file download session for updating this metadata.

So this is not really needed and by default i will still store cache data to device home directory, but advanced users can relocate the sha1hash/peer cache files by modifying /usr/bin/transmission launch script, replacing :

./transmission

with :

TRANS_CACHEDIR=/media/mmc2/yourcachedirname ./transmission