Bug #3457
User interupt in recursive download takes too long
| Status: | Closed | Start date: | 03/15/2013 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | 03/22/2013 | |
| Assignee: | Stavros Sachtouris | % Done: | 100% |
|
| Category: | kamaki | Spent time: | - | |
| Target version: | v0.8 |
History
#1 Updated by Stavros Sachtouris about 11 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
A thread that writes to a local file needs some time to cancel itself. This bug was treated as behavioral issue not as a performance issue.
Each thread is givven 0.5 seconds timeout to cancel, increased by 0.1 for every unsuccesfull round. A round is an attempt to cancel all threads. User is seeing a console message where a . or a * apears on the screen at most every <timeout> seconds, indicating the failure or success of a thread to cancel.
This is not faster than just waiting for threads to finish, but gives the feeling of responsiveness and control.