We are running Silverlight 4 version Web Application same in Silverlight Out Of Browser App but when in Out Of Browser crashes
continuously after some time usage getting message as "Silverlight Out Of Browser Laucher has Stopped Working " and crashes. We have checked Memory usage and it having 530 MB and CPU Usage is 40%.
Is this causing due to any Silverlight plugin issue ? . where as in IE same application works better than OOB app and it crashes rarely but OOB app it crashes continuously . Earlier we have memory leak issue and fixed by implementing proper garbage collection techniques in Dispose method. so its not due memory leak and somethign causes in OOB app that crashes.
Can you any one suggest some possible solutions to avoid following crashing issue or can trace where might causing this issue ? As it is Out of Browser app we cant see page errors . Please suggest some tracing techniques.
Thanks
Krishna
Following IE crashing logs got
Related
We have a Kiosk app which runs on Chrome Kiosk mode and is written in React JS. But for some of our Kiosk machines (All of our machines are Windows machines), it seems to be crashing regularly (Approx. %4 of the devices) without any user input or fixed time between crashes.
I reviewed the code several times but never found any background tasks running, or any reason for the Chrome to crash at all.
Because the crashes are irregular, I cannot connect to a problematic device and wait for it to crash for hours to debug the process. And because the app is automatically started via a VB script when Windows is started, the clients often "solve" the crashes by restarting the Kiosk machine, which is time consuming and leads to tons of complaints.
So my questions are;
Can I somehow force Chrome to restart, or lets say Go to first page in history if it crashes?
Can I catch errors globally without using ErrorBoundries in JavaScript (It is already implemented and is used for other things)
I tried using --remote-debugging-port=9222 to use Developer Tools, but I need to be connected to the machine and go to localhost:9222 port manually to use this and cannot afford to be connected to the device all the time. So is there a way to connect and use Developer Tools on 9222 port remotely?
I tried saving console logs to a file (using Chrome Command Line Arguments) but never saw any "Errors" on the list, so is there any arguments to help me save crash logs to a file to inspect them after the crash?
Thanks for all your help.
I'm failing to find concrete information on troubleshooting Out of memory exceptions for RN apps running on Android. I've been getting some OOM errors reported to my Bugsnag dashboard, all of which seem fishy.
The crashes are occurring on the login screen, before any heavy logic / rendering / etc. occurs.
The reported memory usage is low (one crash occurred with 3MB used by the app). This may not include anything used in the NDK though after emailing Bugsnag.
Available memory is far beyond used memory (though not including what is used by the NDK)
This is not isolated to older devices - one crash occured on a Galaxy S9 with the app using 13MB (plus NDK), and 255MB still available.
I of course enabled largeHeap for the time being while I investigate, but I'm still seeing crashes with this low reported memory usage. The only direction I have is checking if RN is eating up native memory, which isn't reported as 'used memory' in my console.
While profiling my app (using a debug variant APK, not against the development server), I do see the native memory usage seems high - 81mb with the app just sitting for a while after logging in. It hovers around 30-40mb prior to logging in.
I've ensured my code isn't making any API calls or loading resources during the crash workflow. The login is fairly simple, consisting of a gradient, some text and views, and react-native-app-auth being loaded to handle a login. I do not see a spike when performing the authentication in that library.
Are there any tools or methods to check why RN is eating so much native space? Or is this just normal? I'm currently on RN 0.57.5, React 16.6.3. I cannot test on iOs devices to check if this is an Android-specific problem.
did you try this ?
Add this to your "android/app/src/main/AndroidManifest.xml"
<application android:largeHeap="true"
ref: https://github.com/facebook/react-native/issues/6799
After using sometime App crash on User Device which I don't have access to it. I have read the blog about using the CN1Libs-NativeLogsReader to see the error occurred on remote devices. I would need some help on how to use it for this kind of issue for debug builds. Please advise.
That won't save you from a crash as that would be too late in the game.
You can use the API to get the native log but you can't use it to catch a physical crash.
I have been experiencing weird behavior with AngularJS. When I run AngularJS on IE10 my browser become crashed, I have seen my windows processor monitoring it some how multiply memory x time greater with loop and at some stage my browser become halt.
Please advice anything I can do with that.
Thanks
I spent some time debugging a SL3 application with VS 2010 in IE9 beta today and noticed a few quirks. Sometimes when launching the Silverlight app in VS it fails to load in the browser, but refreshing with F5 tends to fix the problem. Also, there are sporadic scripting errors that pop up a debug dialog - these also seem to be fixed by refreshing the page. Has anyone run into these problems and found a fix?
EDIT: My most prevalent error is:
Error: ASP.NET Ajax client-side framework failed to load.
I don't understand why, but someone without a name at the Silverlight forums has found a solution that worked for me:
Just add or uncomment this entry to your hosts file (%SystemRoot%\system32\drivers\etc\hosts):
127.0.0.1 localhost
I noticed this as well with Silverlight 4, but also when I start a simple web project.
IE9 has a shorter startup time that IE8. Debugging a Silverlight application starts the development web server to host the http:// site. The time that it took to start up the web server was less than the time to start up IE8 and greater than the time it takes to start up IE9.
#Michael S. Scherotter - It can't be because of the shorter startup time because making the host file change which fixed it for me would have zero impact on app startup time. Something else must be causing the browser and Cassini to not talk to each other correctly.
One other fix, related to the others is to change the StartURL to launch to the loop back address directly, rather than editing the hosts file. So, in one app, I've got this as the start URL:
http://127.0.0.1.:60525/
Of course, to make this work consistently, I've selected a "specific port" in configuration, as 60525 in this case.
(the trailing . after the loop back address is to allow Fiddler to do its magic).