# Problem with expiring records in memory-only namespace - "n\_bytes\_memory went negative"

**URL:** <https://discuss.aerospike.com/t/problem-with-expiring-records-in-memory-only-namespace-n-bytes-memory-went-negative/2560>\
**Category:** General Discussion\
**Tags:** error\
**Created:** [February 27, 2016, 7:51pm UTC](https://discuss.aerospike.com/t/problem-with-expiring-records-in-memory-only-namespace-n-bytes-memory-went-negative/2560 "2016-02-27T19:51:53Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![brad](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/brad/32/2566_2.png) [@brad](https://discuss.aerospike.com/u/brad)\
**Post date:** [March 1, 2016, 12:43am UTC](https://discuss.aerospike.com/t/problem-with-expiring-records-in-memory-only-namespace-n-bytes-memory-went-negative/2560/6 "2016-03-01T00:43:28Z")

</div>

@akkomar Thank you for the helpful information! The problem was that for UDFs we were not properly accounting for key storage when adjusting the memory usage total on record creation. We’ve fixed this and the fix will be part of an upcoming release.

---

_[View the full topic](https://discuss.aerospike.com/t/problem-with-expiring-records-in-memory-only-namespace-n-bytes-memory-went-negative/2560)._