|
| Re: [CDO] CDOQuery / SessionManager memory leak? [message #890790 is a reply to message #890679] |
Sat, 23 June 2012 03:46   |
|
Am 22.06.2012 22:39, schrieb Per Sterner:
> Hello,
>
> I am having once again a problem :roll: . The Java VM was running wild and memory was full. I identified these
> classes among others:
>
> 42: 43521 1740840 org.eclipse.emf.cdo.internal.common.CDOQueryInfoImpl
> 59: 43521 1044504 org.eclipse.emf.cdo.common.util.CDOQueryQueue
> 60: 43521 1044504 org.eclipse.emf.cdo.common.util.CDOQueryQueue$QueueEntry
> 61: 43521 1044504 java.util.concurrent.PriorityBlockingQueue
> 62: 43521 1044504 java.util.concurrent.locks.ReentrantLock$FairSync
> 63: 43521 1044504 org.eclipse.emf.cdo.common.util.CDOQueryQueue$BlockingCloseableIteratorImpl
> 43: 43520 1740800 org.eclipse.emf.cdo.internal.server.QueryManager$QueryContext
> 51: 43520 1392640 org.eclipse.emf.cdo.internal.server.QueryResult
> 74: 43520 696320 java.util.concurrent.FutureTask
> 75: 43520 696320 org.eclipse.emf.cdo.internal.server.QueryManager$QueryContext$1
>
>
> CDO: 4.1-RC4 (S20120612-1449)
Thankks for testing our RCs ;-)
> I thought I forget to close the CloseableIterator but then I looked where these objects were referenced.
> They are referenced in 'ISessionManager' under the Session.listeners.
Which of the above objects exactly?
> If I produce nice request 20 wait a bit and again 20 the 'Session.listeners' isn't growing.
I can't remember what exactly a nice request is. A linux thingy?
> If I do a brutal loop with 10000, 3320 listeners remain. (In this case I used 'CDOQuery.getResult', but with
> 'CDOQuery.getResultAsync' I have same problem)
Sounds like something we should investigate. Please submit a bugzilla. Is it possible that you copy one of our test
cases and try to reproduce this effect. That would help to get a fix into the first 4.2 M-build.
> Under Mac OS X and Linux I can reproduce this situation. Under Windows It is perhaps harder to reproduce?
I just have a Windows box at hand here. A test case may help to sort out OS-specific behaviour.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01891 seconds
] 
Search
Help
Register
Login
Home
. The Java VM was running wild and memory was full. I identified these classes among others:
