[Soot-list] OutOfMemory of TLO analysis

[Richard L. Halpert]

TLO is quite memory hungry.  You may get better results with builds
from after 2010-07-10, as I made an important scalability change to
the code on that day.  I believe Soot 2.4.0 is too old for that, so
you should try a nightly build.

-Richard

On Fri, Feb 11, 2011 at 1:37 PM, Eric Bodden
<bodden at st.informatik.tu-darmstadt.de> wrote:
> Hi Lei.
>
> I think that's just a scalability problem of the analysis. To the best
> of my knowledge, it was never optimized for low memory consumption.
>
> Eric
>
> On 11 February 2011 12:32, Lei Shang <shangl at cse.unsw.edu.au> wrote:
>> Hi,
>>
>>    I was doing Spark and ThreadLocalObjects analysis for dacapo
>> benchmarks. It runs out-of-memory for eclipse and tomcat, even I set
>> -Xmx10G on a 64-bit Linux server with 16GB physical memory. Is that
>> all right or any memory leaking problem?
>>
>> Lei
>> _______________________________________________
>> Soot-list mailing list
>> Soot-list at sable.mcgill.ca
>> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>>
>
>
>
> --
> Dr. Eric Bodden, http://bodden.de/
> Principal Investigator in Secure Services at CASED
> Coordinator of the CASED Advisory Board of Study Affairs
> PostDoc at Software Technology Group, Technische Universität Darmstadt
> Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
> Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>