My app is already published in the Store, it was built on Windows 8.1 and it perfectly works on 8.1 (desktop and tablet). However it crashes on Windows 10 just after I navigate from page that has a WebView control (though this might not be the reason). I looked at windows logs (eventvwr.msc) and found out the crash has happened in a system library.
Has anybody faced problems with Windows 8.1 apps running on Windows 10?
UPDATE 1: information from system's event log
Faulting application name: ....
Faulting module name: twinapi.appcore.dll, version: 10.0.10240.16397, time stamp: 0x55af0938
Exception code: 0xc000027b
Fault offset: : 0x0001cab9
Faulting process id: 0xe30
Faulting application start time: 0x01d0daabb7ab6d89
Faulting application path: C:\Program Files\WindowsApps.....
Faulting module path: C:\Windows\System32\twinapi.appcore.dll
Faulting package full name: ....
Faulting package-relative application ID: App
UPDATE 2
With help of this article Debugging a Windows 8.1 Store App Crash Dump I've cracked crash dump and found out the problem method in my code. That method has code that captures a screenshot of a web page with webView.CapturePreviewToStreamAsync(memoryStream); and saves it to local file. I suspect webview causes the crash because its core should differ from one on windows 8.1 (is it based on MS Edge instead of IE?).
Related
We recently upgraded our server O/S from Win2012 to Win2019. While on 2012, in IIS, we had configured a Virtual Directory called PDFReader. The physical path was a filestream directory which contains a series of PDFs, which is essentially just a UNC share.
The directory was being called by an SSRS report & its sole purpose was to call the PDF from filestream and render it in SSRS.
We used a simple virtual directory when we were on Windows 2012 which worked fine. But we noticed that the app pool kept crashing on 2019. So that led to me convert it to an application because that way, I could assign an individual app pool to it & manage the rapid fail protection settings as a band-aid for now until we could identify the underlying issue. That has been getting us by.
I tried a few things such as changing the application pool identity to LocalSystem, then a privileged domain user w/SQL Filestream access. I also tried changing the .NET CLR Version to "No Managed Code" and the pipeline from Integrated to Classic. The latter seemed to slow the failures slightly, but nevertheless the problem persists.
Here's the stacktrace which we consistently see every few minutes as users frequently pull up PDFs.
Faulting application name: w3wp.exe, version: 10.0.17763.1, time stamp: 0xa7ccada2
Faulting module name: nativerd.dll, version: 10.0.17763.1, time stamp: 0x84a81d7a
Exception code: 0xc0000005
Fault offset: 0x0000a8f0
Faulting process id: 0x25cc
Faulting application start time: 0x01d921151b65f242
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: C:\Windows\System32\inetsrv\nativerd.dll
Report Id: 88535cc3-8716-40f7-bfab-1f53f9c77b92
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 1192683016347496699, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: w3wp.exe
P2: 10.0.17763.1
P3: a7ccada2
P4: nativerd.dll
P5: 10.0.17763.1
P6: 84a81d7a
P7: c0000005
P8: 0000a8f0
P9:
P10:
There are a number of PDFs that are called which one might consider large, over 20MB with a handful of them over 100mb.
As for the user experience, since I implemented the rapid fail protection, the user doesn't run into the 503 errors anymore, requiring me to start the stopped app pool. Occasionally, when the worker process dies & hands off to the next one spawned, it's a minor delay.
Any help or insight would be appreciated.
Thanks,
Mike
Converted virtual directory to application.
Created/assigned individual app pool to application.
Changed rapid fail protection settings to allow for 25 failures in 10 minutes instead of the 5/5 out of the box.
Changed application pool identity to LocalSystem... Problem persisted. So I changed to a privileged domain user/local admin with proper SQL filestream rights, same behavior.
Ensured nativerd.dll was present in system directory, no discernible permissions issues.
Looked into MaxWebConfigFileSizeInKB registry key associated with nativerd.dll per a Microsoft KB article, but I don't see that key present in the registry.
Ran DebugDiag analysis with this summary result:
In w3wp__PDFReader__PID__160__Date__06_15_2022__Time_08_39_35AM__249__Second_Chance_Exception_C0000005.dmp the assembly instruction at nativerd!INDEXED_ARRAY_LIST::FindEntry+18 in c:\Windows\System32\inetsrv\nativerd.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000038 on thread 6
VS2015 crash, while Run app with Windows Phone emulator, I tried with Phone 8.1 and Windows 10 Mobile Emulator. Emulator launch successfully but VS can't deploy app, end crash.
Faulting application name: devenv.exe, version: 14.0.23107.0, time
stamp: 0x559b7ead
Faulting module name: SirepClient.dll, version: 0.0.0.0, time stamp: 0x559f6024
Exception code: 0xc0000005
Fault offset: 0x0002c376
Faulting process id: 0x3770
Faulting application start time: 0x01d123ea21bcb890
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Phone Sirep\8.1\SirepClient.dll
Report Id: d583c604-2aed-41b5-ac84-8223f613cef0
Faulting package full name:
Faulting package-relative application ID:
Application: devenv.exe Framework Version: v4.0.30319 Description: The
process was terminated due to an unhandled exception. Exception Info:
System.AccessViolationException at
Microsoft.VisualStudio.DeviceConnectivity.Interop.ConManServerClass.ConnectDevice()
at Microsoft.SmartDevice.Connectivity.Device.Connect() at
Microsoft.SmartDevice.Connectivity.Wrapper.ConnectivityWrapper12.CreateConnectedDeviceInstance(Microsoft.SmartDevice.Connectivity.Device)
at
Microsoft.SmartDevice.MultiTargeting.Connectivity.ConnectableDevice.Connect(Boolean)
at
Microsoft.VisualStudio.CommonProject.SmartDevice.Deploy.DeployTask.Execute()
at
Microsoft.VisualStudio.SmartDevice.ProjectSystem.SilverlightMobileVSProjectFlavorCfg.Deploy(System.Object)
at
System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at
System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext,
System.Threading.ContextCallback, System.Object, Boolean) at
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext,
System.Threading.ContextCallback, System.Object, Boolean) at
System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch() at
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
This solved my Windows Phone 8.1 Deploy to Device Visual Studio 2015 crash issue:
1) Shut down Visual Studio.
2) After enabling/unlocking your device (WinPhone 8.)1 for development;
https://msdn.microsoft.com/en-us/library/windows/apps/ff769508
Make sure you download and install the Windows Phone 8.1 SDK.
https://developer.microsoft.com/en-us/windows/downloads/windows-8-1-sdk
3) After installing this SDK, try to connect to your WinPhone 8.1 through the SDK, which will trigger a "Special Update" for that device.
4) After installing the update on your device and it reboots, start Visual Studio and deploy/debug to your device.
This error occurred to me a few months ago and to resolved I have to install the Windows Phone 8 SDK, because the Visual Studio 2015 only installs the Windows Phone 8.1 SDK.
I cannot comment on the previous post to give the answer about the "SDK tool".
But the tool he means is actually the Windows Phone Developer Power Tools. If you connect, it will trigger an update installing the powertools runtime on the device.
Interestingly I ran into that problem after first being successful with deploying to the phone. But after I restarted Visual Studio, I got the deployment crash.
Unfortunately it did not resolve the problem for me.
My libgdx app starts up on ios simulator and shows ios intro libgdx pic, then crashes.
I get:
[ERROR] Session could not be started: Error Domain=NSPOSIXErrorDomain Code=3 "Unable to run app in Simulator" UserInfo=0x7f853960ff60 {NSUnderlyingError=0x7f8539464ff0 "Failed to lookup the process ID of se.myapp.IOSLauncher after successful launch. Perhaps it crashed after launch.", NSLocalizedFailureReason=An error was encountered while running (Domain = NSPOSIXErrorDomain, Code = 3), NSLocalizedDescription=Unable to run app in Simulator}
Seems to be related to trying to run 64bit on iPhone 4s, where it is not supported. Does anyone know how to turn off 64bit for robovm in libgdx?
If I change the ios-sim command:
/Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/robovm-1.4.0/bin/ios-sim launch /Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/build/myapp-ios/myapp-ios/ios/x86_64/IOSLauncher.app --timeout 90 --unbuffered --devicetypeid "com.apple.CoreSimulator.SimDeviceType.iPhone-4s, 8.0" --stdout /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stdout-6250612031367207111.fifo --stderr /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stderr-5592986297298678222.fifo --setenv ROBOVM_LAUNCH_MODE=release --args -rvm:log=warn
To:
/Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/robovm-1.4.0/bin/ios-sim launch /Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/build/myapp-ios/myapp-ios/ios/x86/IOSLauncher.app --timeout 90 --unbuffered --devicetypeid "com.apple.CoreSimulator.SimDeviceType.iPhone-4s, 8.0" --stdout /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stdout-6250612031367207111.fifo --stderr /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stderr-5592986297298678222.fifo --setenv ROBOVM_LAUNCH_MODE=release --args -rvm:log=warn
It works with the old robovm. But for the new version it seems those directories aren't even built at all, so it fails.
Where should I specify the architecture? There is:
<arch>thumbv7</arch>
in robovm.xml but it doesn't seem to do anything?
Has this anything to do with the eclipse integration plugin (I am running from eclipse)?
OK I found out (after about 12 hours of digging)!
I looked in the wrong place all the time. The solution is (in eclipse) to go to Run Configurations / iOS Simulator App / Choose a device and select 32-bit (x86).
I have a working project and it was working quite fine.
All of a sudden I am not able to build my Windows Phone project.
1>------ Build started: Project: win-ladenzeile, Configuration: Debug Any CPU ------
1> Multilingual App Toolkit build started.
1>C:\Program Files (x86)\MSBuild\Microsoft\Multilingual App Toolkit\Microsoft.Multilingual.WindowsPhone.targets(9,5): error : The file exists.
1>C:\Program Files (x86)\MSBuild\Microsoft\Multilingual App Toolkit\Microsoft.Multilingual.WindowsPhone.targets(9,5): error :
1>C:\Program Files (x86)\MSBuild\Microsoft\Multilingual App Toolkit\Microsoft.Multilingual.WindowsPhone.targets(9,5): error : Update XLIFF build failed.
1>C:\Program Files (x86)\MSBuild\Microsoft\Multilingual App Toolkit\Microsoft.Multilingual.WindowsPhone.targets(9,5): error : Multilingual App Toolkit build completed with errors.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
I tried the following:
Disable and re-enable the Multilingual App Toolkit.
Repair the Multilingual App Toolkit.
Reinstall the Multilingual App Toolkit
git reset head --hard
Restart PC couple of times.
I am really confused and can't believe the Visual Studio suddenly started acting weird.
Any help is highly appreciated.
EDIT - (After 18 hours)
I am quite sure this has to do with the Multilingual App Toolkit.
I disabled it in the .csproj file
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\Multilingual App Toolkit\Microsoft.Multilingual.WindowsPhone.targets" Condition="Exists('$(MSBuildExtensionsPath32)\Microsoft\Multilingual App Toolkit\Microsoft.Multilingual.WindowsPhone.targets')" Label="MultilingualAppToolkitForWindowsPhone" />
Also disabled "Enable Code Analysis on Build" as I was getting some errors about Code Analysis.
I hope the next version of the toolkit will fix this bug.
You will see this when you hit the max number of temp files on your system. See: http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1&l=EN-US&k=k(System.IO.Path.GetTempFileName);k(GetTempFileName);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);k(DevLang-csharp)&rd=true
The Multilingual App Toolkit also uses this API and if you are already close to the limit, it can trigger the error.
To resolve this issues, please be sure to clean your %temp% folder to get unblocked.
Had this problem today and it seemed to be because the xlf files used by the Multiligual App Toolkit were not checked out of source control.
The actual problem appears to be the fact that the files are readonly on disk.
I'm opening the default project for Windows Phone 8 using VS 2012 Professional and WP8 SDK, and am trying to configure the Windows Phone 8 WVGA 512 (default) emulator.
Using build and deploy both work. Build and deploy are both checked in the build settings for all build types. The output gives me this:
Deploy started: Project: ABCD, Configuration: Debug x86
Deploying C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap...
Connecting to Emulator WVGA 512MB...
Installing the application...
Deployment of C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap succeeded.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
However if I try to open the Simulation Dashboard to change any settings (Lock Screen -> Unlocked or "Enable Network Simulation", Visual Studio returns the error:
Connection to Windows Phone device or emulator failed.
How do I fix this issue? I have no headway on this problem because there's nothing from Google or stackoverflow, and I've tried a ton of things related to this problem (mainly the fixes for the infamous Could Not Debug Application error.)
Thanks for the help.
I have very similar problem, but in my case the simulation does not work on actual device (it used to, but now suddenly it doesn't). It does work with emulator. Deploying and debugging works fine on both.
This would suggest that it might be more general problem. Not tied to target device type in particular.