#2266 closed Bug (fixed)
Transmission crash in 8780 (DHT?)
| Reported by: | vaska | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | None Set |
| Component: | Transmission | Version: | 1.72+ |
| Severity: | Normal | Keywords: | crash dht mac |
| Cc: | jch@… |
Description
This has happened three times already on two different machines, both Intel Macs running 10.5.7, and all three times it was when all torrents had finished seeding or were otherwise stopped. Attached is a report copied from the most recent crash.
Attachments (2)
Change History (12)
Changed 13 years ago by vaska
comment:1 Changed 13 years ago by charles
does this crash happen in 1.72 as well?
comment:2 Changed 13 years ago by vaska
- Keywords crash dht mac added
- Summary changed from Transmission crashes when torrents are finished (DHT?) to Transmission crash in 8780 (DHT?)
Another crash, this time with torrents running. This is also the first time it's happened while I've been using the computer. Changed summary to not reflect incorrect information.
comment:3 Changed 13 years ago by charles
do you have a crash report from the second crash?
comment:4 Changed 13 years ago by vaska
I'll run 1.72 for a while and see if it has trouble, too. In the meantime, here's the second report.
comment:5 Changed 13 years ago by charles
- Resolution set to fixed
- Status changed from new to closed
I'm going to back out dht 0.7 for awhile and see if that changes anything. a handful of people have had similar bug reports in the nightlies and I haven't heard back from the libdht author yet.
reverted in r8783
comment:6 Changed 13 years ago by charles
Similar crash report from the forums: http://transmission.pastebin.com/m524d3942
vaska: does the crash go away if you upgrade to >= r8783?
comment:7 Changed 13 years ago by vaska
I just saw that change so I was about to try it. 1.72 has been steady as she goes.
comment:8 Changed 13 years ago by vaska
r8784 has been solid so far.
comment:9 Changed 13 years ago by jch
- Cc jch@… added
Charles, how do I decode the dht_periodic + 7255 in the report?
--Juliusz (back from holiday)
comment:10 Changed 13 years ago by charles
jch: sorry I missed this comment before.
Pretty much all we can get from that it that it happened somewhere in dht_periodic. The offset is, I think, indicative of how far into the function it is, It's probably a few thousand instructions in.
If this is the same crash as was fixed in dht 0.8, then it's a moot point. But, if you're asking for the benefit of future debugging, the usual next part of the script is to ask the user to provide a crash report from the nightlies, since they don't have the debugging information optimized/stripped out.
Copied from CrashReporter?