BMediaFile leak (or leakS)
|Reported by:||ttcoder||Owned by:||axeld|
Three leaks (two confirmed) (I'm currently in hrev48619):
- easily confirmed 196 bytes leak in the ctor, using the ten-line test-case .cpp in #9945
- easily confirmed 196 bytes leak in BMediaFile::Track(), using the same (with some semi-random speculation in ticket:9945#comment:9 that the leak might have been introduced e.g. in the low r47000s range)
- got word that our build of SoundPlay used with December hrevs consumes up to 0.6 MB per hour or more (there's a case of 150 MB in a couple days) whereas the same build didn't leak at all when run on early PM builds or 46104 (last non-PM build), but we're still trying to confirm that one. That would be something bigger than a leaked thread of 196 bytes if true, so might be in the media-kit instead of libroot in this third case.. Got to collect more data and confirm, since other variables have changed (the plugins loaded into SP for one).
Tentatively setting above-average priority since this has a significant impact on our users.
Change History (10)
comment:4 by , 5 years ago
|Component:||- General → Kits/Media Kit|
|Priority:||high → normal|