My website http://remotejobs.io crashes Safari consistently. I first noticed the crash last night when I was at a Verizon store and I tried browser testing the site on an iPad. So I tried 2 more iPads at the same store, and the site crashed iOS Safari on all 3 devies, every single time I tried to hit the domain.
The exact workflow is:
Open Safari
Enter http://remotejobs.io
That's it. As soon as you hit go the site crashes.
This also happens on desktop Safari (tested in 6.0.3 on OSX 10.8.3 only), and produces an error report every time. Here's a copy of one of the error reports generated: http://go.jag.is/OGcS
The site is not throwing any JS errors, and works fine on other modern browsers that I have tested, including Chrome, Firefox, and even IE9 (shockingly enough).
One strange thing though, is that it only seems to crash iOS Safari on iPads, not iPhones, as I can successfully load the site on my iPhone every time.
What on earth could be causing this, and how do I debug it?
UPDATE: I tried commenting out the main stylesheet, and the site no longer crashes Safari without that stylesheet. I tried both a regular stylesheet, and a minified stylesheet, and both crash the browser.
UPDATE 2: I narrowed it down to the CSS by commenting out JS and leaving CSS in, and still it crashed. Then I tried removing all the transition properties, and it no longer crashes. So apparently the transition properties were causing the crash.
So I was able to narrow the problem down to the CSS with Adam Moore's suggestion, and then to the transition property declarations with Jonathan Sampson's comment.
I removed all the lines with transition and the site no longer crashed.
So then I looked at the values, and tried unifying the duration values, to see if that would help, since I was setting several different duration values across the different properties, including .5s on one, .3s on another, and .25s on yet a couple more. But unifying them didn't affect anything - still crashed.
Finally, I tried changing the transition-property from all to color, since color was the only thing I was really changing, and no more crashes! So apparently that was the solution. Seems Safari was choking on trying to transition all the properties.
Your website does not seem to crash Safari 5.1 on Windows 7. To go about debugging what's causing the issue, start by turning off the CSS, then one by one disable JS files until the website stops crashing. Once you've figured out which CSS file or JS file it is, then post a link to the file and I'll see if I can help!
I stumbled across the same issue in Safari and tried everything mentioned here. I also checked the css in the CSS validator and fixed some issues.
But my trigger for the crash were padding with percentage values. I converted the %-Values from the paddings and all the things were fine.
-webkit-transform-style: preserve-3d !important;
Caused Safari to continuously reload because of error. Removed that and it worked. :).
Safari - Version 8.0.8 (10600.8.9)
OSX EL Captain
Related
I am using Noto Serif Medium font. Everything works as it should, when I launch the app with a fresh start.
The issue happens when I background the app and open anything that has not been rendered yet.
The classic "Unrecognised font family" error appears.
This error happens on iOS emulator and iOS physical devices.
I have checked targets, resources and Info.plist file in Xcode. Everything is there. Still this error happens.
I suspect that there could be an issue with the .ttf file itself, as you're not able to get this font from Google Fonts directly, even though it is a free to use font.
Is there anyone that can provide a lead to a solution?
This one was a dozzie.
Turns out, that it shouldn't have been working in a first place. It was a classical iOS font name issue. I don't know why it was working when the app wasn't backgrounded, but hey atleast the problem is solved.
Just use the PostScript name, not the real name tag in iOS fontbook.
Every now and then, my iOS simulator becomes extremely slow. Am unable to deterministically say when this happens. One solution seems to be "Reset Content and Settings.." effectively turning off chrome debugging and then restarting the app. Has anyone faced this issue ? If yes, are there any solutions to continue debugging in Chrome without any performance hit.
Didnt face this on the previous versions. Now on ^0.35
React Native console.log will slow everything down if Chrome tab displaying the log messages is not visible. You can try react native debugger and see if you have same issues.
https://github.com/jhen0409/react-native-debugger
Here is my issue:
I've installed phonegap and phonegap desktop.
http://code.riffzone.net/phonegap-install-msw/
Now, when I'm working on my application (Jquery Mobile), I'm testing it on a browser, but the application is reloading again and again after every 2 seconds and I can't even write something in the form input, reloading to fast..
I don't understand where this is coming from?
Here is the screen shot of my browser and the firebug console where you can see the page reloading over and over (1) and the api_auto_reload in the console (2).
Thanks a lot :)
The reload should be triggered only when some of your source files is changed. For some reason it does detect change on your files constantly. That reason is quite hard to find out without debugging more. You can, though, turn the auto reload off with --no-autoreload switch for phonegap serve like this
phonegap serve --no-autoreload
It was phonegap desktop beta (the minimalist server) and not phonegap (command line) which was causing this bug.
If you have the same issue, make sure you are not using it.
We have a fairly large air app, and for some reason, when we package it for iOS, it does not launch correctly. Just a plain white screen. When we launch it in debug mode (or even using Fast packaging), it works fine. Only with the export release build it simply launches a plain white screen and does nothing.
Anybody seen anything similar? Any idea if there is an error of some sort, any way to find out what the error is?
SO it turns out after hours of struggling with this is the issue was loading swf files. We had some embedded Image assets that were swf files, which works great in debug mode, but fails spectacularly in release mode. Given that the app we are working on is a behemoth that takes over 30 minutes to build a release version (on a very powerful box), this was quite a pain to nail down. We finally converted swfs to fxg and the error went away
I've just experienced a similar white screen issue when building an AIR iOS app (in any mode). The app builds and launches with no errors but just displays a white screen after the launch image has disappeared.
This issue was different to the one above but I want to post this here for future reference.
It turns out that this was due to incorrect read/write permissions on the source files. i.e. I had copied the source files onto another computer and then logged into that computer as a different user.
The solution was to simply re-copy the source files onto the computer whilst logged in as the correct user.
I am trying to load an SWF inside a WebView in my cococa app, it works fine when I load an HTML which references the SWF. But i'd like do load the flash file alone, with no HTML. Is that possible??
Yes.
It's broken in currently-released WebKit (even on Snow Leopard), but last I checked, it was fixed in WebKit nightlies, so it'll work again someday.
I finally found an answer for that. It is not quite a fix, but it can get my app working for now.
Every time swf is loaded it make a call to debugger and XCode stops.
According to this post, I should disable the option "Stop on debugger" at run menu in XCode.
Now my project is up and running.
Thanks!