Trying "monitor for leaks" with any windows store app (including the built-in apps) using debugdiag2 update 2 fails.
I get a "Failed to monitor for leaks in .... Please make sure that everyone has read and execute permissions for ...leaktest.dll" message.
I've changed the permissions as indicated and followed the suggestion at:
Troubleshooting native memory leaks in Windows Store applications using DebugDiag and LeakTrack
But no luck.
Works fine for non store apps.
Anyone have this working?
Related
Does anymore same experience or solution for that ?
My app works fine only several days after deployment, after that it turns to blank screen with "Not Found" text on it.
App is with "WildFly Application Server 8.2.1.Final" Cartridge with status "Started" - note that I am aware of iddling of apps at Openshift, this is not the case.
Recieved reply from OpenShift as following :
It looks like you're hosting your app on a small gear. The WildFly cartridge could be quite memory consuming, depending on what app you are deploying. Please check whether the gear is not having memory issues, as described
https://developers.openshift.com/faq/troubleshooting.html#_why_is_my_application_restarting_automatically_or_having_memory_issues
If there seems to be no memory issues, please check your log files for further information about the problem. You can check your log files by using the 'rhc tail' command, or by sshing into your application and looking in the ~/app-root/logs directory.
You can learn more about checking your log files in our Developer Portal (https://developers.openshift.com/en/managing-log-files.html)
We are planning to develop a metro app and wanted to find out what kind of support/programming model is available in Windows8 RT to collect debug/diagnostic log data. This should quickly help/diagnose app errors in the field.
Can we log debug data as we do traditionally in Windows apps and ask user to send the log file when encountering an error ?
For Ex. If the app misbehaves when loaded on the QA/end user machines, we can request QA/end user to attach the log files with the issue.
You don't have to collect any data, windows store is doing that for you. In windows store app Dashboard, under quality you have reports about chrashes and app unresponsive states, these are *.cab files with debug informations.
You can open this file (*.dmp) with Visual Studio, here are the details :
http://msdn.microsoft.com/en-us/library/windows/apps/jj933262.aspx
Have you checked this MSDN sample : Logging Sample for Windows Store Apps (ETW Logging in WinRT) ?
I'm trying to profile my application using Instruments on the device itself. Specifically, I'm trying to do time profiling.
Unfortunately, I just can't get it to work. Here's the situation:
1) If I run instruments with the app signed using the developer profile on the simulator, it works.
2) If I run instruments with the app signed using the distribution profile on the simulator, it works.
3) If I run instruments with the app signed using the distribution profile on the device (which is the default case for profiling since the scheme is set to use the release build) then Xcode complains about that there's no valid provisioning profile. That seems reasonable.
4) If I run instruments with the app signed using the developer profile on the device, then Xcode transfers the app, but then states that it's "Finished running" immediately. The app isn't run, and in most cases there's no error message.
Sometimes, just sometimes, there's a message from the Organiser stating that device does not recognise host - E800001C.
5) Running the app directly using the developer profile works fine - I can debug as expected.
Summary - I can't run an app on a device through Instruments using a debug build - it stops before it's had a chance to start. There are no error messages - nothing at all in the debug console.
Help?
Thanks,
Tim
I've solved this. It hadn't occurred to me to check the console inside the organizer. It said:
: entitlement 'keychain-access-groups' has value not permitted by a provisioning profile
After a bit of Googling I discovered that deleting the app from the device would solve my issue. Now I can profile.
So easy when you know how. Hope that helps someone else.
Tim
First of all app can be executed on simulator without signing it. Now apple has provided us the developer profile to test the app on devices.
Distribution profiles are created for submitting the app to the apple store or when application has to be distributed to the employee within the enterprise.
If want to do profiling on device do it with developer one. It should work.
I'm looking to sandbox an app to comply with the March 1st sandboxing requirement of the Mac App Store. My app includes a built-in terminal emulator which utilizes a forkpty() call to launch processes in a pseudo-tty environment. Unfortunately, this call fails under the sandbox with the error "Operation not permitted", although the fork() call works just fine. Presumably the forkpty() call requires read/write access to the /dev/ directory to create a pseudo-tty (according to the man page). I've tried adding a temporary sandboxing entitlement (com.apple.security.temporary-exception.files.absolute-path.read-write) with read/write access to /, and I now can indeed read and write files anywhere on the file system, but the forkpty() call still fails with the same error. Does anyone know how I might get forkpty() to work under the sandbox?
My app is a programming text editor with a built-in terminal emulator and file browser, so it essentially needs to have access to the entire file system. Apart from the forkpty() problem, this temporary entitlement seems to do what I need. But will Apple accept an app with such a loosely defined temporary exception entitlement?
Thanks in advance guys. I really hope I can get this sandboxing up and running so I continue to distribute my app through the App Store.
It is impossible to implement a useful terminal emulator in a sandboxed application -- even after you add entitlements for the PTY devices, the shell ends up in the same sandbox as the app, preventing it from doing very much.
We have a VB.NET applciation that is run from a mapped network drive. This works fine on all PCs expect those with Windows 7, on those we get the following:
"application generated an exception that cannot be handled" System.Security.SecurityException was unhandled
If the application folder is copied locally and run from there it works fine.
Anyone know a way aroudn this issue? I assume it is related to Windows 7 netowrk security but not sure how to work around it.
Well, normally you should get this error on all PCs, not only on your Win7 PCs. But I guess for your older Windows PCs someone has solved this issue some time ago. Read this article
http://thebackroomtech.com/2009/04/01/using-caspolexe-to-grant-net-applications-rights-to-a-remote-network-share/
how to deal with the problem. Here is an SO post
.NET Deployment to Network Share
which might help you, too.
There is a reason this error comes up, It is not a good idea to grant applications access to network shares just to run them.
.Net and Click Once makes it very easy to deploy an application to a network share and distribute it to all the client computers to be run from there.
The app can then check for updates whenever it is launched and download any changes. You get all the ease of deploying to a shared drive without mucking about with code access security policies and potentially leaving a nasty hole in your network security.