|
|
|
|
The following issue has been updated. |
|
Updater: Olivier Grisel
Date: 22/05/07 23:28
Comment:
As Florent stated, the following should better live as a comment
update:
OG: I found and fixed a non closed CoreSession instance in the IndexingHelper / DocumentIndexableResourceImpl classes that should fix the observed leak.
I have seen that the logout method that should close the Compass session has been commented out. I wonder if it can be responsible of a second memory leak.
We need to write load functional tests to ensure we are no more leaking memory during massive indexations of Nuxeo document resources.
I leave the bug at level Major instead of blocker instead we have written and successfully tested that as part of the tests suite.
|
|
| Field |
Original Value |
New Value |
|
Change By
Olivier Grisel
on 22/05/07 23:28
|
|
Description
|
M2 has a memory leak that makes the application unusable after about 1h of heavy use
update:
OG: I found and fixed a non closed CoreSession instance in the IndexingHelper / DocumentIndexableResourceImpl classes that should fix the observed leak.
I have seen that the logout method that should close the Compass session has been commented out. I wonder if it can be responsible of a second memory leak.
We need to write load functional tests to ensure we are no more leaking memory during massive indexations of Nuxeo document resources.
I leave the bug at level Major instead of blocker instead we have written and successfully tested that as part of the tests suite.
|
M2 has a memory leak that makes the application unusable after about 1h of heavy use
|
|
M2 has a memory leak that makes the application unusable after about 1h of heavy use
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
