You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are facing an issue that zipline leaks 500-600kb every "cycle" of usage.
Is there any examples
of correct usage ZiplineScope and ZiplineScoped?
how we must correctly close services and zipline
how we must correctly close services and zipline when service contains Flows?
We thought that we are doing something wrong with closing pipeline. So we downloaded current world-clock example.
we see continious leaks of memory
sometimes we see lots of messages from EventListener of leaked callbacks
after we close zipline and open next instance we see even more info about leaked callbacks
We modified example
//val serviceName = endpoint.generatePassByReferenceName()val serviceName = endpoint.generatePassByReferenceName() +"____"+ value.adapter.simpleName // to see what object is leaked
Hello
We are facing an issue that zipline leaks 500-600kb every "cycle" of usage.
Is there any examples
We thought that we are doing something wrong with closing pipeline. So we downloaded current world-clock example.
We modified example
After this changes we launch
and some times (even without closing zipline) we see
LEAKED____zipline/guest-8192____SuspendCallback
LEAKED____zipline/guest-8080____SuspendCallback
LEAKED____zipline/guest-7928____SuspendCallback
LEAKED____zipline/guest-8124____SuspendCallback
LEAKED____zipline/guest-8116____SuspendCallback
after closing and reopening screen we can see even more messages of that kind
sample project is at
https://github.com/evtuhovaleksander/zipline/tree/leaks_example
The text was updated successfully, but these errors were encountered: