Exactly, which is why the suggestion to “turn off extensions” to prevent crashes and suggesting that Safari is working alright, is silly. If Safari crashes now then it obviously isn’t ready just yet. All you are doing is avoiding the issue and it’s not something an updated extension will technically solve, it will merely circumvent it, given that the cause of the crash lies with Safari itself. Not all extensions are updated timely after all, if at all. Safari shouldn’t crash because of extensions and if it currently does then it needs to be fixed and until that is done complaints about its crash-proneness are valid.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Sixth OS X 10.11 El Capitan Beta to Developers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Exactly, which is why the suggestion to “turn off extensions” to prevent crashes and suggesting that Safari is working alright, is silly. If Safari crashes now then it obviously isn’t ready just yet. All you are doing is avoiding the issue and it’s not something an updated extension will technically solve, it will merely circumvent it, given that the cause of the crash lies with Safari itself. Not all extensions are updated timely after all, if at all. Safari shouldn’t crash because of extensions and if it currently does then it needs to be fixed and until that is done complaints about its crash-proneness are valid.
Hmm not that i have the products in question, but I wonder if it is a display driver issue, can pople with AEX issues please tell me if they use apple drivers or drivers from the Nvidia/ATI website? My hunch is thaet when el cap is released we will se displey driver updates that wil fix most AEX/premiere issues.
Disclamer: This is jus my personal opinion, I'm no expert and I have no insede info
Or in Windows 10's case, WUDO is kicking in...
http://windows.microsoft.com/en-us/windows-10/windows-update-delivery-optimization-faq
That's my favorite "feature".
I had the software update show up last night, however as it seemed to take forever to download I left it to install overnight. Checked this morning and doesn't appear to have installed anything - doesn't show in the 'recently installed' list and states there are no updates available.
Has the update been pulled or anything like that? Tried the Terminal script stated above but to no avail.
Has the update been pulled or anything like that? Tried the Terminal script stated above but to no avail.
I would, but I don't have access to a Dev account to get the links, plus the other usual places haven't uploaded direct links yet?
Well you shouldn't be using the developer previews if you are not a registered developer. Use the public betas instead.
When you say it works fine, does "folders on top" work?
When you say "temporarily disable SIP" have you re-enabled it again and it still works?
Quick question regarding El Capitan -- in the keynote, they were talking about things like a 1.6x speed increase. However in this thread a lot of people are mentioning that this build is much smoother and generally quicker than the previous one. Plus a lot of people running the first beta said it was already quicker than Yosemite and surprisingly stable for DP1. Are the advertised speed boosts an estimation of the benchmarks on the final build, or will the performance increase be even greater than anticipated?
I hope this makes sense, sorry if this sounds like a stupid question.
I hope this makes sense, sorry if this sounds like a stupid question.
Firstly, crash-proneness is not even word, rather extremely bad grammar. Secondly, do people have to continually point out that this is beta software you are arguing about? Of course Safari isn't ready, IT'S BETA!!! Apple do not have to make THEIR browser compatible with ANY third party extensions, it is the other way around. That's why betas are released for testing, and which is why extension developers update their extensions to be compatible with new software. Apple have blocked certain javascript while in beta testing in the past. Clearly not everyone is experiencing Safari crashes here, which indicates it's symptomatic of something more localised.
First step while experiencing problems while testing BETA software is to turn off plugins or extensions to isolate any issues. I was able to isolate clicktoflash as an issue while testing Yosemite beta. The developer changed to a new clickto plugin but had not updated the old one. A simple deletion of the old extension and an update to the new fixed the issue.
If you recall, Safari had many issues with crashes with redundant and poorly coded Flash plugins in the past which is why they disabled outdated Flash plugins some time ago. Are you arguing that it's Apples responsibility to test 100+ browser extensions to run within Safari now? You obviously haven't developed any software.
Please explain to me why Safari in BETA would crash with an outdated extension turned on, but not crash when it's disabled? Again, remembering it is not Apple job to make its browser comparable with 100+ extensions. Your argument is totally flawed and ridiculous.
A statement like '1.6x speed increase' is meaningless without saying where exactly that increase is expected. If anything, 1.6x is first and foremost a marketing figure. And at the time of keynote they didn't have the current, more polished beta, so it probably refers to some stuff they have measured back then.
That might be right, but at the same time Safari should not crash even if the extension does something wrong, its a managed environment after all. Crashes indicate that there are bugs in the extension API. The correct behaviour is to crash the extension instead.