stief
December 16th, 2007, 09:33 PM
Here are 5 stack traces for issues involving "stuck" downloads. I'm seeing far more issues with 4.15.1 (OS X; Pro) choking on many downloads than in earlier versions. OTOH, I haven't seen the GUI freezes of the past. I had hoped the OS X update to Java 1.5.0_13 would help, but the "stuck" downloads continue.
Here are the notes on what was happening during each of the traces.
--"Saved Terminal Output red incompletes.txt"
This involves downloads that turn red in the Library/Incompletes. These downloads usually have non-English characters in the filename, and I recall zab asked for a stack trace (this may not be a 4.15 issue; IIRC correctly I managed to get this trace several days ago).
--"Saved Terminal Output frozen on connecting.txt"
After noting an unusually high number of downloads stuck on the "Connecting . . . " message in the downloads pane for > 12 hrs, on the third session I grabbed a kill -quit <pid> stack trace from the Terminal. Session 1 had 16/104 "What's new" .jpgs stuck; session 2 had 14/99 downloads stuck; session 3 (this stack trace) had 12/108. A subsequent session had 6/24 stuck.
--"limewire-log downloads stuck on connecting.txt"
Same session as above, but LWConsole com.limegroup.gnutella.downloader.* set to "All"
--"limewire-log stuck on queued.txt"
Same session as above, but stuck downloads cleared from the download pane, then resumed from the Library/Incomplete tab. All stuck on "Queued." 3 of the stuckers started to download, then like the others, stuck on "Queued."
--"limewire-log stuck awaiting 0 secs.txt"
This one was interesting. After using the clear button on the downloads pane, this sole download remained, stuck on a "waiting 0 secs" message. The priority number didn't change from when other downloads were in the list, so the "Priority" number also was frozen and didn't update.
Suggestions for getting better traces welcomed.
Also, with all the new work on developing tests, I'd appreciate knowing why the tests didn't catch these problems.
Here are the notes on what was happening during each of the traces.
--"Saved Terminal Output red incompletes.txt"
This involves downloads that turn red in the Library/Incompletes. These downloads usually have non-English characters in the filename, and I recall zab asked for a stack trace (this may not be a 4.15 issue; IIRC correctly I managed to get this trace several days ago).
--"Saved Terminal Output frozen on connecting.txt"
After noting an unusually high number of downloads stuck on the "Connecting . . . " message in the downloads pane for > 12 hrs, on the third session I grabbed a kill -quit <pid> stack trace from the Terminal. Session 1 had 16/104 "What's new" .jpgs stuck; session 2 had 14/99 downloads stuck; session 3 (this stack trace) had 12/108. A subsequent session had 6/24 stuck.
--"limewire-log downloads stuck on connecting.txt"
Same session as above, but LWConsole com.limegroup.gnutella.downloader.* set to "All"
--"limewire-log stuck on queued.txt"
Same session as above, but stuck downloads cleared from the download pane, then resumed from the Library/Incomplete tab. All stuck on "Queued." 3 of the stuckers started to download, then like the others, stuck on "Queued."
--"limewire-log stuck awaiting 0 secs.txt"
This one was interesting. After using the clear button on the downloads pane, this sole download remained, stuck on a "waiting 0 secs" message. The priority number didn't change from when other downloads were in the list, so the "Priority" number also was frozen and didn't update.
Suggestions for getting better traces welcomed.
Also, with all the new work on developing tests, I'd appreciate knowing why the tests didn't catch these problems.