Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
We are experiencing while list is showing number of Photos and Application crashes with below Logs:
Incident Identifier: 80161CE4-DBFC-4401-B0D9-816FC2C2625C
CrashReporter Key: 0e3845b16122ba9a68170fe8a4385714b90e31c8
Hardware Model: iPhone8,1
Process: DSA.iOS 
Version: 1.4 (1.4)
Code Type: ARM-64 (Native)
Parent Process: launchd 
Coalition: uk.co.nhbc.dsa 
Date/Time: 2017-10-31 15:37:04.1863 +0000
Launch Time: 2017-10-31 15:35:44.1513 +0000
OS Version: iPhone OS 11.0.3 (15A432)
Baseband Version: 4.00.01
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Region Info: 0 is not in any region. Bytes before following region: 4295180288
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
__TEXT 0000000100034000-0000000100070000 [ 240K] r-x/r-x SM=COW ...S.app/DSA.iOS
Triggered by Thread: 0
Application Specific Information:
Is there any Fix available for this BUG?
We need a fix as it's critical for our production release.
Please provide us with a reproduction in order to move forward with investigation. Thanks.
This issue will be closed as no reproduction has been provided nor have any further comments been made. Please reopen this with a reproduction project if the issue still occurs as of the latest 2.5.0 stable release of Forms.
Guidelines for creating reproductions are available at: