View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000544 | XMB1 | Bugs | public | 2019-12-04 14:13 | 2020-10-20 18:17 |
| Reporter | miqrogroove | Assigned To | miqrogroove | ||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.9.8 SP2 | ||||
| Target Version | 1.9.12 | Fixed in Version | 1.9.12 | ||
| Summary | 0000544: Excessive Memory Use in fixlastposts with DEBUG Mode | ||||
| Description | The fixlastposts algorithm requires a separate UPDATE query for each thread, which will consume memory in proportion to the number of stale threads found when in DEBUG mode. This needs to throw a warning message for now. In the long run, it would be slick to figure out how to do this entirely in SQL. | ||||
| Tags | No tags attached. | ||||
| MySQL Version | |||||
| PHP Version | |||||
| Web Server | |||||
| Browser | |||||
| Flags | |||||
| Original Reporter | |||||
| SVN Revision | 2775 | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-12-04 14:13 | miqrogroove | New Issue | |
| 2019-12-04 21:17 | miqrogroove | Assigned To | => miqrogroove |
| 2019-12-04 21:17 | miqrogroove | Status | new => resolved |
| 2019-12-04 21:17 | miqrogroove | Resolution | open => fixed |
| 2019-12-04 21:17 | miqrogroove | Fixed in Version | => 1.9.12 |
| 2019-12-04 21:17 | miqrogroove | SVN Revision | => 2775 |
| 2020-10-20 18:17 | miqrogroove | Status | resolved => closed |
