transmission-remote: Unable to parse response "{"arguments":{"torrents":[{"trackerStats":[{...

[Astara]

Was having trouble with the windows transmission remote gui with it not being able to parse JSON it was gettin back from transmission-remote.

I tried the web-client -- it also says it is having trouble.

Tried the command line -- it seems to be a problem in the json when I try to look at the tracker status of any torrent:

I get: [19:09:15.408] JSON parse failed at pos 722: STRAY_TOKEN -- remaining text ""result""success" [19:09:15.409] transmission-remote: Unable to parse response "{"arguments":{"torrents":[{"trackerStats":[{"announce":"​http://aaaaaaaaa.wwwww.to:3277/announce","announceState":1,"downloadCount":48,"hasAnnounced":true,"hasScraped":true,"host":"http://aaaaaaaaa.wwwww.to:3277","id":0,"isBackup":false,"lastAnnouncePeerCount":50,"lastAnnounceResult":"Success","lastAnnounceStartTime":1367114882,"lastAnnounceSucceeded":true,"lastAnnounceTime":1367114883,"lastAnnounceTimedOut":false,"lastScrapeResult":"","lastScrapeStartTime":1367114890,"lastScrapeSucceeded":true,"lastScrapeTime":1367114891,"lastScrapeTimedOut":0,"leecherCount":185,"nextAnnounceTime":1367116683,"nextScrapeTime":1367116700,"scrape":"http://aaaaaaaaa.wwwww.to:3277/scrape","scrapeState":1,"seederCount":22,"tier":0}]}]}"result""success""tag"9}

Not sure what is causing this yet...any ideas how to track it down?

version 2.75

[jordan]

There were changes to the JSON generation between 2.75 and 2.77. Does this bug still happen in 2.77?

[x190]

See also #5158 and #4882.

Forum Post by OP: ​https://forum.transmissionbt.com/viewtopic.php?f=8&t=14713 "I saw 2.77 was available and tried it as well -- same thing."

[Astara]

Unfortunately, yes.

It made no difference.

I tried 2.77 after filing and noted it prompted me for 2.77 -- so thought it would be worth a try...

There are longer log examples but, for me anyway, no more revealing of the problem attached to the transmission-remote bug db @ ​http://code.google.com/p/transmisson-remote-gui/issues/detail?id=655, where I first reported this. The author of that util pointed at a bug involving unicode, but I don't see any unicode in the above text. As unicode was thought to be the problem w/bug 4882, I thought this might be a different problem. Thus a new report instead of adding to that one.

[Astara]

Following up to my previous comment, I would note that the bug report mentioned had an attached wireshark conversation, which also shows the corrupt output the daemon was sending to the client.

[mike.dld]

The issue is caused by non-threadsafe operations on recycled list nodes in libtransmission. Attaching a patch which fixes it for me. Related issues mentioned in comment:2 may also be fixed.

[jordan]

r14182: make accessing tr_list's recycle nodes threadsafe. patch by mike.did, fixes #5352