UWP app random crash

Nimalika 21

Our UWP app crashes in release mode randomly.

Windows event viewer shows following exception codes

Faulting module name: edgeIso.dll, version: 11.0.18362.836, time stamp: 0x23127c72
Exception code: 0xc0000409

Faulting module name: dcomp.dll, version: 10.0.18362.836, time stamp: 0x1ca78712
Exception code: 0xc0000409

We found that code: 0xc0000409 indicates a stack buffer overflow. How can we fix these types of exceptions? We tried handling UnhandledException to get more info on these exceptions but app crashes without calling it in release mode.

Thanks.

Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,851 Reputation points

2020-07-27T09:33:49.677+00:00

Does app crash in the debug model? And we can't confirm the issue with above information. you'd better provide your app's min and target version OS version and the specific exception info.
Nimalika 21 Reputation points

2020-07-27T09:59:22.05+00:00

Didn't notice these crashes in debug mode.

Min Version : Windows 10, version 1809 (10.0:Build 17763)
Target Version : Windows 10, version 1903 (10.0:Build 18362)
OS : Windows 10 Home version 1903 (64-bit)

Only place I could get any details about these crashes are from Windows Event Viewer. Those logs don't provide much details. Any idea how I can get more details on these crashes that happens in release mode?

Thanks.
Nico Zhu (Shanghai Wicresoft Co,.Ltd.) 12,851 Reputation points

2020-07-27T10:54:16.09+00:00

For release version, we suggest you use AppCenter to catch exception and view it in app's dashboard. And you could also use try-catch block to catch the exception and print it with message dialog
Nimalika 21 Reputation points

2020-08-06T09:18:34.547+00:00

We tried to use AppCenter but when we install Microsoft.AppCenter.Analytics and Microsoft.AppCenter.Crashes NuGet packages got conflicts with sqlite-net-pcl. Found that there are some incompatibilities of those packages with sqlite-net-pcl. We can not use another library for sqlite connection at this point. Is there any other way for us to get more details about these exceptions? These are not getting caught with try catch blocks we added. We get these info from windows Event Viewer only.

Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.959
Exception code: 0xc000027b
Fault offset: 0x0000000000713500

Faulting module name: edgeIso.dll, version: 11.0.18362.959
Exception code: 0xc0000409
Fault offset: 0x000000000002f875