[android-developers] Re: inefficient garbage with large heap = true

bob wrote: > Yes, malloc and free are oldies but goodies. > Uhhh ... > I remember meeting malloc back in like 1991. It didn't want to give me more than 64k back then, but it is nicer to me now. Fond reminiscence doth not a sound engineering basis make. I find the suggestion to switch to nati

[android-developers] Re: inefficient garbage with large heap = true

Yes, malloc and free are oldies but goodies. I remember meeting malloc back in like 1991. It didn't want to give me more than 64k back then, but it is nicer to me now. On Wednesday, November 14, 2012 1:07:00 PM UTC-6, Lew wrote: > > bob wrote: > >> Maybe you can use native code and use ma

[android-developers] Re: inefficient garbage with large heap = true

bob wrote: > Maybe you can use native code and use malloc and free? > Really? -- Lew -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this gro

[android-developers] Re: inefficient garbage with large heap = true

Maybe you can use native code and use malloc and free? On Saturday, November 10, 2012 11:58:01 AM UTC-6, elihan wrote: > > I have an app with large heap set, running on a galaxy S3 GT-I9300, with > android version 4.1.1 > The app needs to allocate a lot of temporary objects intermittently. >