View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0022010 | MMW 5 | General | public | 2026-03-05 17:23 | 2026-03-05 18:54 |
| Reporter | michal | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | unable to reproduce |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2024.2.1 | ||||
| Target Version | 2024.2.1 | Fixed in Version | 2024.2.1 | ||
| Summary | 0022010: Random crashes with SDHasher in callstack | ||||
| Description | We receive crashreports for many months, where object TSDHasher is often in callstack, but there is no clear reason why it crashed (usually Access Violation during usual work with hasher). I've found out, it is most probably related to the situation, when some track was removed from the database some time before. We should better handle it in the hasher to avoid inconsistent state of the hasher. Note, that it is problematic to reproduce, as the crash is fairly random. But we should see, whether it helped, in future crashlogs. Last crashreport with this case had ID 42940000. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3212 | ||||
