SourceForge.net Logo
Main Overview Wiki Issues Forum Build Fisheye
Issue Details (XML | Word | Printable)

Key: CMP-717
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Shay Banon
Reporter: Jaroslaw Lewandowski
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Compass

OutOfMemory in long running transaction

Created: 25/Sep/08 08:37 AM   Updated: 25/Sep/08 09:20 AM
Component/s: Compass::Core
Affects Version/s: 2.0.0 GA
Fix Version/s: 2.1.0 RC


 Description  « Hide
I faced a problem with long running transaction in which a CompassQuery is executed many times.
I found that even when I call CompassHits.close() the reference to the hits and all retrieved documents are kept in AbstractTransaction.delegateClose.. so in long running transaction I have an effect of memory leaking, the more queries and more results in response the memory is used... and actually I can't free it by myself.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Shay Banon added a comment - 25/Sep/08 09:20 AM
You are right. Compass now removed the closeable instance from the list once an explicit close is called.