Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#589 closed Bug (fixed)

1.00: completion.c:174: failed assertion `piece <tor>info.pieceCount'

Reported by: charles Owned by: charles
Priority: Normal Milestone: 1.01
Component: libtransmission Version: 1.00
Severity: Major Keywords:
Cc:

Description (last modified by charles)

http://www.transmissionbt.com/forum/viewtopic.php?t=3535 Prax

Click on the icon... within a moment it crashes. Rinse. Repeat.

1.0 release doesn't work latest nightly doesn't work

.96 (4441) doesn't work

.96 (4122) release works

Process: Transmission [535]

Path: /Applications/Internet/Transmission?.app/Contents/MacOS/Transmission

Identifier: org.m0k.transmission

Version: 1.00 (4479)

Code Type: PPC (Native)

Parent Process: launchd [116]

Date/Time?: 2008-01-06 00:17:01.326 -0600

OS Version: Mac OS X 10.5.1 (9B18)

Report Version: 6

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Crashed Thread: 4

Thread 4 Crashed:

0 libSystem.B.dylib 0x943244a4 semwait_signal_nocancel + 8

1 libSystem.B.dylib 0x94323f70 nanosleep$NOCANCEL$UNIX2003 + 176

2 libSystem.B.dylib 0x94315108 usleep$NOCANCEL$UNIX2003 + 68

3 libSystem.B.dylib 0x9433a7bc abort + 92

4 org.m0k.transmission 0x0006833c eprintf + 76

5 org.m0k.transmission 0x000572c8 tr_cpPieceRem + 144

6 org.m0k.transmission 0x0004e3c0 tr_torrentSetHasPiece + 68

7 org.m0k.transmission 0x00055d7c recheckThreadFunc + 424

8 org.m0k.transmission 0x0004ff64 ThreadFunc? + 80

9 libSystem.B.dylib 0x94255bf8 _pthread_start + 316

1/6/08 12:16:38 AM [0x0-0x2e02e].org.m0k.transmission[527]

/Users/mitchell/Desktop/Transmission_1.0x/libtransmission/completion.c:174: failed assertion `piece <tor>info.pieceCount'

Change History (4)

comment:1 Changed 15 years ago by charles

  • Status changed from new to assigned

comment:2 Changed 15 years ago by charles

  • Description modified (diff)

comment:3 Changed 15 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

1.0x: r4562 trunk: r4561

Okay, though mocking up some fake torrents I was able to reproduce this myself. It appears that what triggered this bug was torrents whose next-to-last file ended on a piece boundary, and whose last file had a size of zero bytes.

comment:4 Changed 15 years ago by charles

  • Priority changed from High to Normal
  • Severity changed from Normal to Major
Note: See TracTickets for help on using tickets.