search

LLNL / blockbuster

Automatically exported from code.google.com/p/blockbuster
1 stars 1 forks source link

Blockbuster does not release frame memory #64

Open wealthychef1 opened 9 years ago

wealthychef1 commented 9 years ago

When loading a movie that is 64GB uncompressed, blockbuster memory grows to 64GB, leading to the probably conclusion that memory is not being released for frames until the movie is changed. When a new movie is loaded, the memory reduces appropriately.

Original comment by: wealthychef1

wealthychef1 commented 9 years ago

I know this was intentional a while back because fiddling with the cache is fraught with design implications. Basically, the fundamental cache design in blockbuster is so broken it demands a total rewrite to really fix. Given the impact of this bug, I'm wanting to ignore it as it only happens on certain machines sometimes with certain movies. But before I do, I need to check with Scott and Adam to make sure it's really as unnecessary as I think.