Opened 8 years ago
Last modified 8 years ago
#5968 new Bug
Crashing After 'Remove When Finished Seeding' Activated
| Reported by: | fozzy | Owned by: | livings124 |
|---|---|---|---|
| Priority: | Normal | Milestone: | None Set |
| Component: | Mac Client | Version: | 2.84 |
| Severity: | Normal | Keywords: | seeding, crash |
| Cc: |
Description
Also, assertion failure message:
Transmission[395]: *** Assertion failure in +[NSEvent startPeriodicEventsAfterDelay:withPeriod:], /SourceCache/AppKit/AppKit-1348.17/AppKit.subproj/NSEvent.m:3812
Hi, I'm running v2.84+ (7/13/15 nightly) on MacOS 10.10 (Yosemite) and am encountering an issue when I set the option to 'Remove when finished seeding' under the Management tab. When I limit an individual torrent's ratio and have it transferred to a different folder when finished downloading (through the 'keep incomplete files in' function), and the torrent finishes seeding, the torrent successfully removes itself, but crashes Transmission immediately afterwards.
This issue is consistent, and doesn't depend on what ratio number I set. It also doesn't depend on whether 'Stop seeding at ratio' option is activated or not.
At first, I wasn't sure that the torrent was removed (or transferred), but the Mac confirms this with a notification that seeding had been completed, and I don't see said torrent any more upon reopening Transmission (and the file appears in the expected folder).
(I tested for the issue without the file transferring, and the crash still occurs, so the issue is not likely related to moving the file after download.)
I've been encountering the same issue with stable 2.84.
I suspect that the problem is similar to this but the issue seems to be marked as closed, so maybe it's a new thing.
Change History (4)
comment:1 Changed 8 years ago by mike.dld
- Component changed from Transmission to Mac Client
- Owner set to livings124
- Version changed from 2.84+ to 2.84
comment:2 follow-up: ↓ 3 Changed 8 years ago by x190
comment:3 in reply to: ↑ 2 ; follow-up: ↓ 4 Changed 8 years ago by fozzy
Is there anything the end user can do to prevent this from happening? (short of disabling the 'remove when finished seeding' option)
comment:4 in reply to: ↑ 3 Changed 8 years ago by x190
Replying to fozzy:
Is there anything the end user can do to prevent this from happening? (short of disabling the 'remove when finished seeding' option)
Can you edit code and build Transmission?
We likely need to get fireCompletenessChange () back down to just before tr_torrentSetDirty (tor) in tr_torrentRecheckCompleteness (tr_torrent * tor) (Line 2200: libtransmission/torrent.c), as it was in r13880.
Changed by jordan in r14125 and r14123.