My apologies Vince,
I didn't take a close enough look to notice that you were using the same
key. There's certainly something unusual going on there.
On Tue, Nov 24, 2009 at 1:42 PM, Vince Bonfanti wrote:
> But in the testcase I attached to the issue report, I'm doing a put of the
> same key ev
But in the testcase I attached to the issue report, I'm doing a put of the
same key every time--why would this take more and more memory (and never
release it)? Shouldn't the value be replaced, and the memory for the
previous value be freed?
Vince
On Tue, Nov 24, 2009 at 1:30 PM, Toby Reyelts wr
I've posted a reply to the issue, which I'm copying below:
Unlike production, the dev_appserver's memcache implementation has a
100M limit which
it will happily attempt to fill, regardless of how much heap space you
actually have
free in your JVM. You can either increase your heap size to accomoda
There appears to be a memory leak with the memcache implementation on the
dev server; I've opened a new issue for this:
http://code.google.com/p/googleappengine/issues/detail?id=2428
I have some testcases that make heavy use of memcache that are failing due
to this issue.
Vince
--
You received
