You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Supriya Kumar Shyamal <su...@artnology.com> on 2007/03/12 19:40:57 UTC

Possible Memory leak in CSIndexInput

Hi All,

I have a question regarding the close() CSIndexInput class, why there is 
no close operation defined...
Like ...
base.close()

If I analyze the memory dump of  our server I can see lot of object of 
type CSIndexInput. So I am not sure if I call close() on IndexeSearcher 
it closes all index accessing objects.

Thanks,
supriya

-- 
Mit freundlichen Grüßen / Regards
 
Supriya Kumar Shyamal

Software Developer
tel +49 (30) 443 50 99 -22
fax +49 (30) 443 50 99 -99
email supriya.shyamal@artnology.com
___________________________
artnology GmbH
Milastr. 4
10437 Berlin
___________________________

http://www.artnology.com
__________________________________________________________________________

 News / Aktuelle Projekte:
 * artnology gewinnt Ausschreibung des Bundesministeriums des Innern:
   Softwarelösung für die Verwaltung der Sammlung zeitgenössischer
   Kunstwerke zur kulturellen Repräsentation des Bundes.

 Projektreferenzen:
 * Globaler eShop und Corporate-Site für Springer: www.springeronline.com
 * E-Detailing-Portal für Novartis: www.interaktiv.novartis.de
 * Service-Center-Plattform für Biogen: www.ms-life.de
 * eCRM-System für Grünenthal: www.gruenenthal.com

___________________________________________________________________________ 


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Re: Possible Memory leak in CSIndexInput

Posted by Chris Hostetter <ho...@fucit.org>.
:
: I have a question regarding the close() CSIndexInput class, why there is
: no close operation defined...
: Like ...
: base.close()

i'm not expert on this kind of thing, but since CSIndexInput only reads
from a portion of another IndexInput, closing base seems like a bad idea
... super.close() might make sense, but not base.close() i don't think.


-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org