[Exist-open] "Possible lock problem: thread" - leading to java heap error

[Joe W. <jo...@gm...>]

Dear eXist list,

I've been noticing that my local copy of eXist has been gradually
taking up more and more memory, eventually leading to a java heap
error.  This happened as soon as within 1 hour of starting eXist.
Eventually I've had to force eXist's java process to quit, and upon
restarting eXist it has had to reindex.  As I look through the logs
for clues, I've seen lots and lots of these:

"2010-06-02 18:11:48,397 [qtp1069531064-26] WARN
(ReentrantReadWriteLock.java [release]:305) - Possible lock problem:
thread Thread[qtp1069531064-26,5,main] released a lock on
/db/newdesign/js it didn't hold. Either the thread was interrupted or
it never acquired the lock. The lock was owned by: null"

Could these accumulated "possible lock problems" on a threads lead
eXist to run out of memory?

My eXist is 1.5dev rev. 11624, and it has -Xms128m -Xmx1024m, with
db-connection values of cacheSize="128M" collectionCache="24M"
database="native" pageSize="4096" nodesBuffer="-1"
cacheShrinkThreshold="10000".  This has happened both on my 4GB RAM
iMac and 2GB RAM MacBook Air.

Thanks for any ideas,
Joe