This is still present. Was hoping some of the event work we did a week ago would fix this but it didn't.
1) launch metro fx
2) switch to another ap
fx crashes before receiving the suspend event.
I'm working on this, what a strange crash :(
Created attachment 623247 [details]
Callstack when there is a crash
Created attachment 623248 [details]
Call stack from within the suspend callback when there is no crash
Benjamin, Brian's planning to write something up for the report. We'll plan on filing beginning of next week assuming we don't have a break through between now and then.
support entry page is here -
There's no windows 8, so I just selected win7. They route us to the right place.
for secondary options:
1) I use it as an IT Professional, developer or Microsoft partner
2) Internal windows based applications and components (drop down)
3) Base windows services
after that they need the msdn support account info.
We're working on a metro style enabled desktop browser which makes use of XAML interop via a SwapChainBackgroundPanel.
Since we started using XAML interop, we started getting crashes on suspend.
We think that it is related to a bug outside of our code.
The crash does not always happen, but it usually does.
You can reproduce by opening our app, switching to classic Desktop, and then waiting 10 seconds.
When the crashes happen our Suspending event callback is not hit.
Here is the callstack when it crashes:
When the crash does not happen, our Suspending event callback is hit.
Here is the callstack when it does not crash:
The relevant code can be found here:
And in particular see /widget/windows/winrt/MetroApp.cpp
Should also mention that this is what comes up in the debug/output window:
First-chance exception at 0x772C33A5 (ntdll.dll) in fennec.exe: 0xC0000005: Access violation reading location 0x00000000.
Unhandled exception at 0x772C33A5 (ntdll.dll) in fennec.exe: 0xC0000005: Access violation reading location 0x00000000.
I'm working on a fresh test build with all the latest code changes and the xaml interop, should have an install up on the wiki by Monday.
To test this out you can see this build: 5-14 build
MS has reproduced this issue and expects a fix for the release preview.
MS said that they are no longer supporting XAML interop and I verified this is fixed after reverting XAML interop.