Opened 19 years ago
Closed 19 years ago
Last modified 19 years ago
#2011 closed defect (fixed)
Backend deadlock, multiple delete threads waiting on mutex. — at Version 1
| Reported by: | Stuart Auchterlonie | Owned by: | danielk |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.20 |
| Component: | mythtv | Version: | head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description (last modified by )
The backend deadlock with multiple (33) Delete Threads waiting on a mutex.
Full backtrace is attached (it's at the end of the file, there's a short backtrace first, then a thread summary)
Change History (2)
by , 19 years ago
| Attachment: | backend-stuck.log.bz2 added |
|---|
comment:1 by , 19 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
Not a bug.
These threads are waiting for their turn. Only one delete proceeds at a time so we can rate limit deletes. If a large file delete happens due to an auto-expire or user request and then you do a lot of channel flipping, many small deletes will bunch up waiting for the delete lock. Within a few minutes they will all get their turn and execute quickly.
Note:
See TracTickets
for help on using tickets.
backtrace of stuck backend.