Closed ivoflipse closed 10 years ago
I've added a call to model.put_session so whenever a new session is selected, we nuke the cache. However, this does not affect self.measurement and the like, but at least they won't be able to 'get' anything.
For now memory usage seems in hand. By reducing the size of the array's I allocate and creating just one average, instead of a list of all possible paws certainly reduced the memory load.
While this might rear its ugly head again, for now its closed.
Like some of the memory issues I've had before, it seems that when I load more measurements (for example when adding a new subject or new session), memory usage starts to pile up. Make sure you clean up anything that's being cached, so we don't keep things in memory we don't actually use.