sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #03401
Re: [Question #160893]: help debugging leaking script
Question #160893 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/160893
RaiMan posted a new comment:
as far as I understand:
-- bar=foo()
- makes the foo object and creates the instance variables
-- bar.main()
- the existing instance variables of foo are used and
- the newly created region reference (region.exists(img)) overwrites the old one
- the old region reference should be eligible for garbage collection
- no need to do anything from your side
BTW:
-- immutable as such has nothing to do with garbage collection. it only means, that an object cannot be changed in place. "Changing" immutables always means creating a new object.
--- java command line options
-- there seem to be (besides the heap options -Xms/-Xmx) some more options to influence the internal usage of the heap related to GC.
-- some logging can be ordered (not tested ;-)
-verbose:gc # gc info displayed
-Xloggc:file # gc info written to file
-- this is a nice article on Java GC
http://javarevisited.blogspot.com/2011/04/garbage-collection-in-java.html#.Tfr7-M3Qbw8
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.