| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | More lsan suppressions | Christian Mollekopf | 2018-07-30 |
| | | |||
| * | More lsan suppressions | Christian Mollekopf | 2018-07-30 |
| | | |||
| * | more slan suppressions | Christian Mollekopf | 2018-07-30 |
| | | |||
| * | Removed ResourceAccess::Private leak and resolved resulting memory | Christian Mollekopf | 2017-11-16 |
| | | | | | | | | | | corruption. It looks like the memory corruption (malloc started to crash) was coming QLocalSocket related signals. According to the docs it's not safe (whatever that means), to delete a QObject with pending signals, so we use deleteLater to schedule it's deletion. This resolved the crashes. | ||
| * | lsan suppressions | Christian Mollekopf | 2017-11-14 |
| | | |||
| * | qrand is leaking it seems? | Christian Mollekopf | 2017-11-14 |
| | | | | | perhaps just not properly instrumented. | ||
| * | Suppress the known ResourceAccess leak | Christian Mollekopf | 2017-11-12 |
| | | |||
| * | lsan leak suppressions | Christian Mollekopf | 2017-11-12 |
| We get a lot of known "leaks" from lmdb. Some are willingly (we never close the environment and dbi's), others are likely because lmdb itself is not instrumented. | |||
 |
index : sink | |
| A data access layer handling synchronization, caching and indexing |
| summaryrefslogtreecommitdiffstats |
path: root/suppressions.lsan