[Canola] Canola2 beta8 killed by flickr (memory)

[petreken]

Lately I have been crashing canola w/the photocast. If I run one of the killer feeds -- I believe particular photos cause the problem -- memory usage rises until the kernel kills the app. I don't know if I have a hardware problem or if this a bug. Before I figure out how to debug this I would like to know others can read the feed (crafted to have 1 photo in it as I write):

http://api.flickr.com/services/feeds/photos_public.gne?tags=british,smoke,cantante&lang=en-us&format=rss_200

or as a tinyurl:

http://tinyurl.com/6hvgfb

[abond]

I have tried it several times on my 810... locks up every time...

[amigokin]

Lately I have been crashing canola w/the photocast. If I run one of the killer feeds -- I believe particular photos cause the problem -- memory usage rises until the kernel kills the app. I don't know if I have a hardware problem or if this a bug. Before I figure out how to debug this I would like to know others can read the feed (crafted to have 1 photo in it as I write):

http://api.flickr.com/services/feeds/photos_public.gne?tags=british,smoke,cantante&lang=en-us&format=rss_200

or as a tinyurl:

http://tinyurl.com/6hvgfb

Try to hide some pictures in order to find out which ones are causing Canola to crash

[handful]

Hi petreken: indeed: if the photo is too big :; bye bye. It kills and the worst : most of the time we are not able to receive a warning, or a message "out of memory" so we cannot do much about it, until we can receive this message from the platform. (AFAIK)

So it looks that the image is : 4192px × 3354px

Now while this image has only 410kb, when you "load" it to your memory its MUCH more than that : /

So, canola of course needs memory, then if you load this on the browser.. and go back and forth just once or even move the image around a little bit.. it also crashes the default browser :/

Concluding: we are trying to do a "graceful" error, but as you said, the kernel kill us even before we abort the load :/ so... unfortunately we cannot do too much about this : /

Marcelo

[petreken]

So canola fetches the image tagged in the RSS by media:content, not the image tagged by media:thumbnail. In both cases the height and width are provided as attributes. Would it be possible to estimate the memory required and grab the thumbnail instead if the "real image" is expected to eat too much memory?

[handful]

With flickr? there's no way to estimate :) if so we would have placed in the first time :) we don't like to "know" a crash situation and do nothing :) and if we grab only the thumbs then you would get even smaller thumbs then inside the photo viewer... and also : a lot of feeds (we don't know why is not consistent) only send the medium pictures (that looks rather small on the tablets)

: /

Marcelo

[petreken]

Thanks for spelling it out for me. Too bad I can't just stick more memory in the n810. Maybe I'll make a swap file.