View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000603 | LDMud 3.5 | Runtime | public | 2009-01-29 02:31 | 2011-02-14 16:26 |
| Reporter | zesstra | Assigned To | zesstra | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | x86_64 | OS | MacOS X | OS Version | 10.5.x |
| Fixed in Version | 3.5.0 | ||||
| Summary | 0000603: Detect and log too long executions in terms of execution time | ||||
| Description | There are several arguments for and against detecting too long executions based on CPU time spent on it (e.g. the lack of deterministic behaviour). A feature which would be quite unobstrusive but very helpful for tracking lags is to detect too long execution threads and log them including the stack trace (+ plus this_player(), this_interactive(), query_command(), ... etc.). That could reconcile the dispute somehow because no execution is aborted, but necessary information for tracking it later is retained. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-01-29 02:31 | zesstra | New Issue | |
| 2009-01-29 02:32 | zesstra | Relationship added | related to 0000092 |
| 2009-10-06 04:04 | zesstra | Relationship added | duplicate of 0000456 |
| 2011-02-14 16:26 | zesstra | Note Added: 0001981 | |
| 2011-02-14 16:26 | zesstra | Status | new => closed |
| 2011-02-14 16:26 | zesstra | Assigned To | => zesstra |
| 2011-02-14 16:26 | zesstra | Resolution | open => fixed |
| 2011-02-14 16:26 | zesstra | Fixed in Version | => 3.5.0 |
