#2162 closed Bug (fixed)
.resume file doesn't get saved often enough
Reported by: | noelbush | Owned by: | charles |
---|---|---|---|
Priority: | High | Milestone: | 1.74 |
Component: | libtransmission | Version: | 1.61 |
Severity: | Major | Keywords: | |
Cc: | noel@… |
Description
I am running Transmission 1.61 (8385) on Ubuntu 9.04 64-bit, kernel 2.6.27-14-generic.
I love Transmission and thank you so much for it.
That said, I have a long-running problem. It seems that, unless I am able to quit the program very carefully, under just the right circumstances, it loses state information on my torrents when exiting, and when I start back up, I have to run "Verify Local Data" on all or most of my torrents. Since I try to be a good torrent citizen, and have an average of 150 torrents active, that winds up taking a lot of time.
It does seem that, if I have a working network connection, and if I choose "Quit" from the "Torrent" menu, and if I wait until the message about sending totals to trackers closes, then most of the time I avoid this problem. But sometimes I get it even then. And it definitely occurs if my session ends abruptly, or even if my network connection dies.
What then occurs, when I start up, is that some majority -- often all -- of my torrents appear to be at 0% complete, and an enormous amount of activity starts up as Transmission is apparently trying to re-download every one of those torrents. I have to quickly select all, then pause, then choose "Verify Local Data". Once the verification is going, I can click Start on the selected torrents again, and once the verification is complete, they start seeding (or continue downloading, as the case may be). But this really can take a whole day.
Is there any hope for avoiding this problem? I love Transmission so much for all its other characteristics -- that it isn't a resource hog, that it's fast, streamlined with features, etc. But this event occurs often enough for me that it's quite a headache. Please let me know what information I can provide or what tests I can perform to help troubleshoot.
Change History (8)
comment:1 Changed 13 years ago by noelbush
- Cc noel@… added
comment:2 Changed 13 years ago by charles
- Component changed from Transmission to GTK+ Client
- Owner set to charles
comment:3 follow-up: ↓ 4 Changed 13 years ago by charles
comment:4 in reply to: ↑ 3 Changed 13 years ago by noelbush
Replying to charles:
noelbush: thanks for your kind words about Transmission. I like it, too. ;)
about the bug: I haven't been able to reproduce this. Do you have any suggestions on to go about causing this to happen?
Hi Charles,
I have indeed been able to reproduce this on a fresh system. I just installed Ubuntu 9.04 on a new box and fired up Transmission with some new torrents. Sure enough, a buggy graphics driver locked up the machine and I had to restart -- when I came back, I experienced the symptoms described above. So I guess the best way to reproduce this is just to have some torrents running -- preferably at least one complete/seeding, and one still in process -- and then just reboot the machine in a very ungraceful manner.
comment:5 Changed 13 years ago by charles
- Component changed from GTK+ Client to libtransmission
- Milestone changed from None Set to 1.74
- Priority changed from Highest to High
- Severity changed from Critical to Major
- Status changed from new to assigned
- Summary changed from state information lost on (improper?) shutdown to .resume file doesn't get saved often enough
Saving the .resume file periodically, if there's been a change to the .resume state, should clear most of this up.
xref: #2317
comment:6 Changed 13 years ago by charles
- Resolution set to fixed
- Status changed from assigned to closed
fixed in trunk by r8910 for 1.74
comment:7 Changed 13 years ago by charles
revised in r8930
comment:8 Changed 12 years ago by sim
(deleted spam)
noelbush: thanks for your kind words about Transmission. I like it, too. ;)
about the bug: I haven't been able to reproduce this. Do you have any suggestions on to go about causing this to happen?