diff options
| author | Tkachov | 2016-03-04 22:21:11 +0600 |
|---|---|---|
| committer | Tkachov | 2016-03-04 22:21:11 +0600 |
| commit | 9515d07f003854ee4816a56b9b2a709aafc8fdf0 (patch) | |
| tree | a3dabfe8d93a8d2c699ddd88fc61a5ac3084ff90 /engines/tinsel | |
| parent | 445980f010e236edf7af19673f4f01f5ed5a97ab (diff) | |
| download | scummvm-rg350-9515d07f003854ee4816a56b9b2a709aafc8fdf0.tar.gz scummvm-rg350-9515d07f003854ee4816a56b9b2a709aafc8fdf0.tar.bz2 scummvm-rg350-9515d07f003854ee4816a56b9b2a709aafc8fdf0.zip | |
SWORD25: Fixed "Resource not released" warnings [GSoC]
(Look https://sourceforge.net/p/scummvm/bugs/6980/)
The warning messages were appearing because when PRECACHE_RESOURCES is
not defined, ResourceManager's `requestResource()` was used to manually
"cache" them. When you do that, ResourceManager "locks" the resource
once, so you must `release()` it later.
Resources were not released, and warnings appeared. When you
`release()` resource, it still is loaded ("cached"). Resource's
`getLockCount()` is 0, though, so it might be unloaded by
ResourceManager if there is a lot of resources.
Diffstat (limited to 'engines/tinsel')
0 files changed, 0 insertions, 0 deletions