It may be a newb questions, but still.
I'm working on iOS 6 application for iPhone and iPad, and i'm working on hybrid application Javascript\UIWebView + Objective C
The problem is that i have an internal exception in Private framework. This exception is caused by something that is inside a Javascript\UIWebView. And i don't know what Javascript code causing an exception.
So i wan't to do this:
1) Somehow "skip\shallow" crash
2) Using remote Safari debugger, get some info from application
So my question is, is there a way to "skip\shallow" crash, to make my application work for at least few seconds.
I think your only chance to deal with this is by placing log traces all over your javascript, so you can track down where the crash is happening.
To do this, you might find useful this S.O. post showing how you can have JS log to your Xcode console.
Related
I’ve been developing a game which uses WebGL for rendering, and while on PC I get no crashes, on Android/IoS devices I get random crashes during gameplay.
I don’t see any particular areas that would cause crashes, however it still does.
Considering the conditions and frequency that it occurs, I’m thinking it could be a memory leak or allocation failure, but I can’t find a way to analyze this for sure.
I’ve tried changing browsers, so on Chrome/Firefox/Safari it crashes, but on Opera or Armorfly it doesn’t. Additionally, according to the browser the symptoms are different.
I’m using textures (about DreawCall: 70~100, createTexture: 120~200) which draws over 500MB of VRAM, so I’m also thinking it could be that the GPU’s garbage collection isn’t doing its job in time.
The problem is that I can’t find any sort of values or logs anywhere to help me diagnose the problem.
I’ll list the symptoms more closely here:
On Android, while using Chrome, on the Android Debug Bridge’s logcat the error does not show up in the log.
On crash, no error codes or anything appear on the screen.
When I try to remotely debug it using Developer Tool on my PC, again no errors appear in the console.
Similarly, when using IoS and Safari, nothing in Instrument’s log.
So here are my questions:
In this situation, how am I meant to debug and find the problem?
Is there anybody that’s had these sorts of problems? If so, how did you solve it?
Is there any advice I can be given that I can pay more closer attention to when developing the program?
Thanks
We have a webapp that is very javascript intensive - a lot of activity with custom markers on google maps and potentially a lot of items on the page.
Intermittently and unpredictably, Safari on iOS will give the 'A problem occurred with this webpage so it was reloaded' error.
The majority of the time, this happens after a photo has been input and resized by the broswer - an upload hasn't happened yet.
In researching potential issues, I've found the following links
https://discussions.apple.com/thread/6707626?tstart=0
https://www.quora.com/When-Safari-says-A-problem-occurred-with-this-webpage-so-it-was-reloaded-what-sort-of-problem-has-likely-occurred
The real question is how do I identify the cause of the crash? This never occurs on desktop so working out if it's an iOS limitation, a memory issue, a resizing problem or another cause is incredibly difficult.
I've connected an iPhone to a Mac to run the web inspector on the phone but this crash just terminates the whole process without logging any errors so there is no help there either.
Also, there is no reliable way to reproduce the issue - it just happens 'sometimes' with no consistent feature as to what the cause may be.
Thanks in advance.
You've tried this? :
connect your Phone to your Mac and
start xcode
open Window->Organizer->Devices tab->Console and see if there are Errors while reproducing the issue.
I am the developer for a large enterprise website, after the upgrade to chrome 32 the website stopped working completely. I Get the 'aw snap' about the time we have to render most of the elements on the page.
Its a massive code base so i haven't been able to find what's causing it. Ive been booting chrome in debug mode and watching the logs there.
Wierd behavior:
1)If i disable flash it works, we are using swfobject with a flash library.
2)I sometimes see in the logs when it crashes "Uncaught RangeError: Maximum call stack size exceeded" so i must have a infinite loop, but its not a always thing.
3)If i refresh enough it will boot all the way up, and work for good until i kill tab and start over. But again thats a sometimes cause it may start the crash cycle again after a few refreshes.
4) I sometimes see the error "file_descriptor_set_posix.cc(22)] FileDescriptorSet destroyed with unconsumed descriptors" Which i think relates to a infinite loop in the rendering of the webpage which would relate to the maximum call stack exceeded error.
Does anyone know what has changed in Chrome Version 32 that would be a good starting place to find the bug?
Libraries used: SWFobject, Backbone, underscore, soundmanager.js
I dont know why this fixed it, or what chrome changed that caused the code to break but if anyone is interested in what we did to resolve the error i'll explain.
1) I made all events going out of swfobject and our swf code go directly to the Flash.js class we had to interface with flash. Before it was propagating through a Backbone.dispatcher to the flash class. That caused the aw snap error to go away.
2) We were using a datetime library called Moment.js version 2.2.0. It was the one throwing the maximum call stack error, after updating that to 2.3.0 it stopped. Would love to know what chrome changed to cause a infinite loop.
If anyone has info on what chrome changed between the two versions that caused either error, I would love the answer because its a bit scary fixing the symptoms but not knowing the cause.
chrome will open multi tasks in the task manager, and it is sensitive to many plugins
try the following
1- go to settings in chrome
2- open extentions
3- disable all the extensions that you can
4- close chrome
5- open task manager in windows
6- go to processes
7- close all the processes related to chrome
8- reopen chrome and check your problem again
i have built a HTML5 web site (or rather webapp as you wish) and it works fine in Chrome and firefox. I would say the only thing out of the ordinary is, that it uses
Google Closure in some parts (the issue persists in the simplest, non-optimized mode)
HTML5 canvas for 2D drawing
Now I was curious whether it would run on my Galaxy Tab Tablett and indeed it does. I was able to set up the remote debugging facility https://developers.google.com/chrome-developer-tools/docs/remote-debugging?hl=de and debug my code to get rid of a few things that were not working properly. However I notice that android-chrome regulary crashes while I use my app. The console in my desktop browser then complains about websocket being closed (thats why I suspect it really is a problem of the tablet side).
I would like to know what makes my website crash and am a bit flubbergusted that my HTML/js site can crash a browser like chrome so easily. I would have thought that it should be more stable than that.
Now as I would like to have an "entry" point into debugging the issue:
is there a crash log of chrome for android that I can inspect somehow?
can I somehow make it (chrome or android in general) more verbose on error messages?
There are a couple of things that you can do:
chrome://crashes will list the crashes that it has caught when a tab crashes - you might need to turn on crash reporting in the settings. You won't be able to fix it but you will be able to report it us so we can see if it is an issue.
Use logcat and see if there are any specific issues in the tracing output, such as an out of error message.
I'm getting a NO_MODIFICATION_ALLOWED_ERR error using a jquery library on an iPhone & iPod (but not the iPad Emulator, Chrome, Firefox or Safari). As I understand it, this error is caused by either manipulating the DOM when its not ready or adding invalid XHTML if strict checking is in force (which it seems to be on iPhone from what I gleaned from other searches).
So, my question is - is it possible to get the JS stacktrace on iPhone so I can identify what bit of my code is causing this problem? I have Xcode and the iPhone SDK on a Mac, but I don't have much experience - so if someone could point to some way to use this it would be great.
Thanks, Kevin.
for useful debugging on an iOS device, try this: http://phonegap.github.com/weinre/
it may not give you a good stack trace but it will at least let you inspect the app better.
some code explaining what's going on might be useful.
I don't know of any tracing software but maybe - probably stating the obvious - insert some console.error("Error: ") or console.log("Info..") lines in your code?