Closed SLaks closed 11 years ago
Holy crap! I'm gonna test this on Habit today, this may be the holy grail!
This alone will not solve server memory leaks.
Leaking models will consume far more memory than only data.splits
;you should really try to remove the leak entirely.
Also, this will only do anything when those models emit a cleanup
event, which by default only happens every 128 event handler registrations.
I see. I thought the leaky model was only a result of data.splits
build up, I got ahead of myself :)
data.splits
is a big (in memory consumption) part of a model, but the rest of the model (the actual data, the query descriptors, etc) is even bigger.
I handled the model
cleanup
event to empty thesplits
cache.This fixes #72.