FYI the process seems to have changed, board reports are due first of the month
(if you have to report that month) to give people time to review.
I can handle the report if nobody else, but I won't be able to do it for a day
or so
I was wrong, analyzer does have the close function. I closed my analyzer,
but the steady climb in memory is still there.
I wonder if I should create a global analyzer variable and enclose it in a
lock to make sure there isn't any thread issues and use that instead.
Could it be a leak in the
You said pre 2.9.3 I checked the apache lucene.net page to try to see if
I could get a copy of 2.9.3, but it was never on the site, just 2.9.2.2 and
2.9.4(g). Was this an un-released version? Or am I looking in the wrong
spot for updates to lucene.net?
Thanks for all your help
On Tue, Nov 29,
FYI, 2.9.4 can be compiled against .Net 2.0 with a few minor changes in
CloseableThreadLocal
(like uncommenting ThreadLocalT class and replacing extension-methods
calls
with static calls to CloseableThreadLocalExtensions)
DIGY
-Original Message-
From: Christopher Currens
OK, here is the code that can be compiled against .NET 2.0
http://pastebin.com/k2f7JfPd
DIGY
-Original Message-
From: Granroth, Neal V. [mailto:neal.granr...@thermofisher.com]
Sent: Wednesday, November 30, 2011 9:26 PM
To: lucene-net-dev@lucene.apache.org
Subject: RE: [Lucene.Net] Re:
If I recall it correctly, last memory leak problem for 2.9.2 was reported in
~August from RavenDB, and it was fixed in 2.9.4(g)
DIGY
-Original Message-
From: Christopher Currens [mailto:currens.ch...@gmail.com]
Sent: Wednesday, November 30, 2011 11:33 PM
To:
... and it was related with CloseableThreadLocal (fixed in 2.9.4(g)) which
now creates
compilation problem against .Net20 :)
DIGY
-Original Message-
From: Digy [mailto:digyd...@gmail.com]
Sent: Thursday, December 01, 2011 12:09 AM
To: 'lucene-net-dev@lucene.apache.org'
Subject: RE:
The december board report has been updated:
http://wiki.apache.org/incubator/December2011
Please review and adjust as needed,
~P
