Bug 42847 - UWP App Crashes When Resizing Window and Current Page Has a Map
Summary: UWP App Crashes When Resizing Window and Current Page Has a Map
Status: RESOLVED DUPLICATE of bug 41900
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.3.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-07-27 18:13 UTC by Jimmy [MSFT]
Modified: 2016-07-29 01:56 UTC (History)
5 users (show)

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


Attachments
repro project (94.38 KB, application/zip)
2016-07-27 18:13 UTC, Jimmy [MSFT]
Details


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:
Status:
RESOLVED DUPLICATE of bug 41900

Description Jimmy [MSFT] 2016-07-27 18:13:33 UTC
Created attachment 16801 [details]
repro project

### Overview
Trying to resize a UWP app window when the current page contains a map will cause the app to crash with:

> Exception thrown at 0x76FDDAE8 (KernelBase.dll) in ItronMasterDetail.UWP.exe: 0x40080201: WinRT originate error (parameters: 0x8000FFFF, 0x00000016, 0x0603ECC0).
> System.Exception: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))The thread 0x1bc has exited with code 0 (0x0).
> STATUS_STACK_BUFFER_OVERRUN encountered

This seems to happen when the map page is inside a NavigationPage but not when it's the root page. It also does not happen is the map page is pushed modally.

I was able to get some sort of stack trace which seems to point to the crash coming from the native Windows assemblies, so I'm not 100% sure that this is a bug with Forms: https://gist.github.com/jimmgarrido/f394aa6f4bb94e9ad0610382736d2076

I found a SO post with a similar "Catastrophic failure" error from the MapControl in a native UWP app that mentions the issue was fixed by an update to Windows: http://stackoverflow.com/a/33582281/6457998

If I run the same attached repro project on a machine running the upcoming Windows 10 version 1607 update, the app _does not_ crash.


### Steps to Reproduce
1. Run the attached repro project on Windows 10
2. Click "GotoMap"
3. Resize the window


### Expected Results
The window will resize.


### Actual Results
The app will crash.


### Testing Info
Tested with Forms and Forms.Maps 2.3.0.107.


### Workaround
Push the map page modally instead.
Comment 2 FieldstrikeMobile 2016-07-28 08:43:24 UTC
I am also seeing this bug
Comment 3 Samantha Houts [MSFT] 2016-07-28 17:20:36 UTC

*** This bug has been marked as a duplicate of bug 41900 ***