Memory warnings & crashes

[r3econ]

So, I loaded 180 images (about 500Kb each). And after I viewed about 15 app crashed (: Memory level is not normal (63%).).

I guess the memory handling is not done in a right way.

[gdavis]

Are you loading the images into memory before FGallery requests them?

[gdavis]

And are you loading from the network or disk?

[ghost]

I experienced the same issue by loading multiple images from the web. just added additional image URLs to the networkImages NSArray in your example. Memory Usage is growing fast and then the App crashes Is there another way to handle a high amount of pictures loaded from the web?

[ernani]

I am having the exact same issue, I am testing within an iPhone 3Gs with iOS 5.1.1.

It seems it doesn't like much about the preloading threads, after some usage, it crashes and the available memory gets knocked out.

UPDATED: If using this component on a UINavigationController, I was able to manage the memory by handling the cleanup of images and threads on viewDidDisappear, this way my memory keeps fresh on each viewWillAppear.

[ghost]

How did you do that? Are you using the code from the memory warning method?
thanks

[ernani]

I don't have the access to the code for now but will keep your notificaiton
here on my email and will update the message later with the details on my
code, sounds good?

Cheers

On Fri, Jan 4, 2013 at 8:29 AM, acaserop notifications@github.com wrote:

How do you did that? Are you using the code from the memory warning
method?
thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-11878964.

[ghw311]

Application crashes on loading too many images in iPhone，why?

[ernani]

It depends on the size of the images and also the amount of images you are displaying in a grid, also I'd recommend optimizing the methods I've suggested up above.