Bad descripor and corruption errors (not fixed)

Ask for help and report issues with the Mac OS X version of Transmission
Post Reply
quaternio
Posts: 5
Joined: Thu Apr 09, 2009 5:16 am

Bad descripor and corruption errors (not fixed)

Post by quaternio »

UPDATE: My problem has recurred even with the nightly build. My transfer fails, citing "bad descriptor" errors. ANY HELP would be much appreciated. New message log from transmission:

Code: Select all

2011-03-27 16:30:00 -0500 peer-mgr.c:1773 [Error] [FILENAME]: Piece 3262, which was just downloaded, failed its checksum test
2011-03-27 16:30:02 -0500 peer-mgr.c:1773 [Error] [FILENAME]: Piece 2910, which was just downloaded, failed its checksum test
2011-03-27 16:30:05 -0500 peer-mgr.c:1773 [Error] [FILENAME]: Piece 1128, which was just downloaded, failed its checksum test
2011-03-27 16:30:14 -0500 peer-mgr.c:1773 [Error] [FILENAME]: Piece 1701, which was just downloaded, failed its checksum test
2011-03-27 16:30:16 -0500 inout.c:139 [Error] [FILENAME]: write failed for "[FILENAME]": Bad file descriptor
2011-03-27 16:30:16 -0500 torrent.c:487 [Error] [FILENAME]: Bad file descriptor (/Users/~/Downloads/Transmission/[FILENAME]
2011-03-27 16:30:16 -0500 inout.c:139 [Error] [FILENAME]: write failed for "[FILENAME]": Bad file descriptor
Original post
With the latest point release, I was constantly receiving "bad descriptor" errors, preceded by corruption errors (on HFS+ drive). Nightly build 12244 seems to have resolved this issue (it has certainly helped). Below is what I believe is the relavent log from Console.app:

Code: Select all

3/26/11 1:46:40 AM	Transmission[19278]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x100325c40
3/26/11 1:46:44 AM	Transmission[19278]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x100325c40
3/26/11 1:48:36 AM	Transmission[19278]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x100325c40
3/26/11 1:48:41 AM	Transmission[19278]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x100325c40
3/27/11 3:28:52 AM	Transmission[4286]	*** __NSAutoreleaseNoPool(): Object 0x114b49f80 of class NSCFString autoreleased with no pool in place - just leaking
3/27/11 3:28:52 AM	Transmission[4286]	*** __NSAutoreleaseNoPool(): Object 0x118386560 of class NSPathStore2 autoreleased with no pool in place - just leaking
3/27/11 3:28:52 AM	Transmission[4286]	*** __NSAutoreleaseNoPool(): Object 0x114be8ff0 of class NSPathStore2 autoreleased with no pool in place - just leaking
3/27/11 3:28:52 AM	Transmission[4286]	*** __NSAutoreleaseNoPool(): Object 0x114b89410 of class NSCFArray autoreleased with no pool in place - just leaking
3/27/11 3:30:34 AM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10033f270
3/27/11 3:30:37 AM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10033f270
3/27/11 3:30:42 AM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10033f270
3/27/11 3:30:46 AM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10033f270
3/27/11 3:30:50 AM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10033f270
3/27/11 3:30:55 AM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10033f270
3/27/11 3:31:04 AM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10033f270
3/27/11 12:15:01 PM	Transmission[4286]	-[NSTextFieldCell setHover:]: unrecognized selector sent to instance 0x10034c170
Didn't save the Transmission log, but the problem seemed to always be a corrupted packet, followed by "bad descriptor" errors.
I hope I've provided enough info to be helpful; it is a rare occasion that I am truly forced to resort to a nightly build, but this problem finally came to a head when I couldn't DL past 10% of a large file. So, I thought I'd share what caused me to resort to such. Thanks.
Again, please help. Thanks in advance.
Post Reply