Mapper items not tracked when there are no post-commit functions for MetaMapper
See this discussion thread: http://groups.google.com/group/liftweb/browse_thread/thread/35245dcd781c4d1b
Symptom:
I found that when creating mapped objects and saving them within a loop, the object references are retained indefinitely and are thus not garbage collected, leading eventually to out of memory errors.
This only happens if S.addAround(DB.buildLoanWrapper()) is used.
This was raised in the Google discussion group, and in David Pollak's words:
"If there are no post-commit functions defined for the MetaMapper,
we won't track Mapper items for the non-existent post-commit functions. "
Symptom:
I found that when creating mapped objects and saving them within a loop, the object references are retained indefinitely and are thus not garbage collected, leading eventually to out of memory errors.
This only happens if S.addAround(DB.buildLoanWrapper()) is used.
This was raised in the Google discussion group, and in David Pollak's words:
"If there are no post-commit functions defined for the MetaMapper,
we won't track Mapper items for the non-existent post-commit functions. "
Leave a comment
(In revision:86818f45114e6a7dc4d6c9a7962a7ec0c7445e75) Closes #541. If there are no post commit functions, then don't retain the instance
Branch: master
Branch: master
(In revision:3828e1fc7a5f4612c439833eeec2fe6c5a39905e) Closes #541. If there are no post commit functions, then don't retain the instance
Branch: master
Branch: master