I agree, looks like a memory leak to me, I was able to mitigate the
problem, but I hope this issue at least gets officially recognized as
a bug, and eventually fixed.
Mark
On Feb 27, 12:56 pm, Mark Murphy <mmur...@commonsware.com> wrote:
> bra...@gmail.com wrote:
> > I have to agree. I am literally calling
>
> > recycle() on every bitmap
> > then I set them all to null
> > then I run Garbage collection
>
> > I can edit maybe two images and then death. If I reduce the size of
> > the final image I can edit more - but still dies. After the force
> > close it seems like the memory gets freed and I can edit again.
>
> > If that aint a memory leak I dont know what is.
>
> > On Feb 26, 5:36 pm, mark.ka...@gmail.com wrote:
> >> I'm just saying there have been a number of threads on this issue,
> >> I've had out of memory problems when processing bitmaps, and so have
> >> many other developers. It looks to me like a bug IMHO. I hope this
> >> problem will be resolved at some point.
>
> Solving your problem will be faster if you can supply a sample project
> that demonstrates the phenomenon. Post an issue tohttp://b.android.com
> with the sample project, and mention the issue number here once it's
> posted. That way, we can take a look at what you are doing and see if we
> can replicate the problem, if there are other ways of potentially
> mitigating it, etc.
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
> _The Busy Coder's Guide to Android Development_ Version 2.0 Published!- Hide
> quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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 group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
