[Soot-list] Experiences with memory consumption of FlowDroid

[Steven Arzt]

Hi Bernhard,

I was able to analyze Facebook, which is to the best of my knowledge the 
largest application available in the play store today, with 75 GB of 
memory. In general, the larger and the more complex the app is, the more 
memory you need. We know that this is a problem at the moment and we're 
looking into how to reduce the memory footprint - but this is a research 
direction of its own that might include changing the underlying 
machinery from IFDS to something else - so don't expect any major 
breakthroughs in a day.

Can you give me the exact command-line you have used since I have 
updated the wiki a few days ago and have added the --nopaths option? I 
also need the FlowDroid outputs (stdout and stderr) to analyze the 
problem.

Best regards,
   Steven

Am 10.06.2014 07:51, schrieb Bernhard Berger:
> Hi guys,
> 
> I’m trying to analyze some Apps with FlowDroid (latest nightly builds)
> and have some serious memory problems. :-( I picked some random Apps
> from Google Play and tried to analyze them. Sadly, my process gets
> killed by the OOM-Killer. I tried to reduce the memory consumption by
> using all options mentioned in [1].  Nevertheless, the process hits
> the -Xmx limit of 60g after some time.
> 
> What is your experience? How much RAM do I need to analyze Android
> Apps using FlowDroid?
> 
> 
> 
> Regards, Bernhard
> 
> [1] 
> https://github.com/secure-software-engineering/soot-infoflow-android/wiki
> 
> _______________________________________________
> Soot-list mailing list
> Soot-list at CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pubkey.asc
Url: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20140610/cb04cc46/attachment.asc