There isn't really a point in this. Security happens at the process level. If that underlying memory gets unmapped from the processes and mapped to another process, the kernel will take care of things.
On Tue, Jun 16, 2009 at 1:25 AM, Christian Kuester <[email protected]>wrote: > > Hi List, > > I'm digging through the code of the dalvik vm, to see what happens > to free'ed objects and if some kind of memory wiping/cleansing occurs. > > Supposing I would want to ensure that free'ed objects are also cleaned > by (let's say) memset(..,0,..), so that the GC takes care of sensitive data > to be cleaned from the heap: > Would that be possible or can it happen that some objects are never free'ed > (in a bug free world) even if they are not neccessary for core components? > > Christian > > > > -- > tarent Gesellschaft für Softwareentwicklung und IT-Beratung mbH > > Heilsbachstr. 24, 53123 Bonn | Poststr. 4-5, 10178 Berlin > fon: +49(228) / 52675-0 | fon: +49(30) / 27594853 > fax: +49(228) / 52675-25 | fax: +49(30) / 78709617 > > Geschäftsführer > Boris Esser, Elmar Geese > HRB AG Bonn 5168 > Ust-ID: DE122264941 > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them.
