Bug 17652 - Unable to load large image on iPod, application get crashed
Summary: Unable to load large image on iPod, application get crashed
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 7.0.6.x
Hardware: PC Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2014-02-07 07:43 UTC by narayanp
Modified: 2014-02-07 14:46 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description narayanp 2014-02-07 07:43:22 UTC
Steps to reproduce:
1. Download project from link: http://docs.xamarin.com/recipes/ios/content_controls/scroll_view/use_a_scrollview/
2. Extract project and open it in X.S
3. Add image of size 10000 × 6500 pixels in project and set Build action to content
4. In ScrollViewController.cs file.
5. Debug or run the application on iPod touch.

Actual Result: Application does not display image and crashed on iPod Touch. While on other devices this is working fine.

Expected Result: Application should displayed image on iPod Touch

Supplement info:

Device info:
iOS Simulators working
iPad3 version 6.1.2 working
iPhone 4S version 6.1.3 working
iPhone 4s version 7.0.7 working
iPod Touch version 6.1.2 Not working

Environment details:
All Mac
X.S 4.2.3(build 54)

Note: This issue came from Bug 14464
Comment 1 Sebastien Pouliot 2014-02-07 08:36:48 UTC
That looks like a simple out-of-memory condition. 

Some* iPod Touch have less memory (512kb) than newer devices (all others you listed have 1GB RAM).

* you did not specific which generation you used

> Feb  7 18:00:59  ReportCrash[470] <Notice>: Saved crashreport to /Library/Logs/CrashReporter/LowMemory-2014-02-07-180059.plist using uid: 0 gid: 0, synthetic_euid: 0 egid: 0

In fact just by looking at your device log you can see that that the crash report** was named "LowMemory*".

** Just to be 100% sure please symbolicate and attach the crash report to this bug report.
Comment 2 narayanp 2014-02-07 10:08:03 UTC
hi Sebastien,

iPod we used is 4 generation with Model no. is A1367
crash Report: https://gist.github.com/saurabh360/c1dc1a8c177ec8e534d7
Comment 3 Atin 2014-02-07 12:58:36 UTC
An update to the above issue:

Crash Logs from Xcode:  https://gist.github.com/saurabh360/9bcc4c7936bde7bb2744
Exception details: https://gist.github.com/saurabh360/d4e378a0284fe80ea550
Comment 4 Sebastien Pouliot 2014-02-07 14:46:17 UTC
@narayanp Thanks. That confirms it's a memory issue. The sample was not meant to handle such a big image (and does not check if enough memory is available) on older devices. IOW this is not an issue with XI itself.

FWIW I'm not sure there's not much values in modifying the samples data (that might find sample issues - but it does not really help XI itself) but you might want to check with PJ about this.

@Atin whenever you see the following

Exception Codes: 0x000000008badf00d

^ 8badf00d (ate bad food) it means the watch dog killed the application. This is generally because the UIApplicationDelegate did not return control to iOS within 20 seconds. 

And, very often, that's because there's a breakpoint inside the UIApplicationDelegate. Other times it's because it's really taking too long (old devices are slower) but this is an application issue (not a XI issue).