10.11.4 Safari freeze

This is absolutely identical to my problem. The fact that Apple are not resolving this or admitting it's an issue is very poor.

But then the company has fallen on hard times ... they made a couple of $ billion short of their usual $ Kzillion ;-)

Seriously though ... this is very clearly a known problem for many many users ... wouldn't it be mature for them to own up & admit this issue exists?

MacBook Pro (Retina, 13-inch, Early 2015) 2.7 GHz Intel Core i5 - 8 GB 1867 MHz DDR3 - Intel Iris Graphics 6100 1536 MB

RUNNING OSX 11.4

HAS ANYONE HAD ANY HELP FROM APPLE ABOUT THIS YET? IS THERE ANYBODY IN APPLE?

I have also just filed a report to OSX Feedback ... they need to deal with this.

If you haven't already ... please file a simple report here:

http://www.apple.com/feedback/macosx.html

Everyone here seems to have the same problem. Safari, mbp retina 2015, 10.11.4, i would like to add that i had never experienced this problem when i first got my mac back in september 2015. I dont remember which update but it was a lengthy one, the freezing started the same night I updated. We need to keep this thread alive if apple is going to do anything about this silly issue.

Actually I told apple about the thread and they said they don't read these. so its not doing anything but helping each other.

In which case Jonnyakamu anyone really interested in dealing this problem must drop a note here (which only takes a minute or so)

If you haven't already ... please file a simple report here:

http://www.apple.com/feedback/macosx.html

Ok here’s what I’ve found. The Core Service ‘disnoted’ is causing the problem for me. It hogs all the processes power and everything else hangs. Couldn’t work out why it was random but discovered Time Machine sets it off (not every time though) and I had time machine running in the background, it does hourly backups. I’ve put Time Machine off and just do a manual back up at night. I keep Activity Monitor open all the time with the ‘user’ process ‘distnoted’ highlighted and the inspector window open. When I do the backup if ‘distnoted’ kicks off (doesn’t always show on Activity Monitor) I hit the ‘Quit’ then ‘Force Quit’ on the inspector window. This kills ‘distnoted’ then it re-launches and everything goes back to normal. I also shut the iMac down at night, used to always leave it on. So far this has worked for me and hopefully until Apple get a fix.

Hi Dod60 ... that sounds like a serious piece of detective work! I'm a composer and use a Big Mac Pro in the studio which has Time Machine sitting in the background the whole time. However my Freeze issue is with my MacPro 2015 13 inch Retina where I'm really lazy with Time Machine and usually remember to plug it in around once every fortnight! I'm having freeze problems when I'm out and about - so not running Time Machine ... therefore I can't initiate the problem in the way you do.

As far as I've researched on Support Forums there do seem to be a large percentage of people (on many threads) all talking about this issue specifically using 13 inch MacBook Pro 2015 Retina laptops ... not to say that this isn't happening elsewhere ... just that there seem to be a particularly huge number using OSX 11.4 with that specific model.

Hi dick the flick, there’s no doubt this is an Apple software problem and is effecting many people in different ways. If this continues to work for me then I’m going to sit on 10.11.4 until I’m 100% sure the next update has a fix, as at least for me it’s managable. The next update might not be!

I made some statistics just for this thread.

(I know there are dozens of times more treads with this problem just in this forum.)

The memory size and the chipset (Brodwell, Haswell) seems not to have any relation to the problem, also not a single graphic card version.

Although the majority of affected systems(89%) uses an integrated Intel graphic card (neither Intel Iris Graphics 6100, Intel Iris Graphics 6000, Intel Iris Pro Graphics 6200 or Intel Iris Pro 5200). The same majority of systems are also models from 2015.

A bit strange in this view are the 3 iMacs since they not using an Intel graphic card or at least not using them from user point view. The CPU of iMac17,1 and iMac11,2 have an Intel® HD Graphics 530 and Intel® HD Graphics on the chip. After some research in internet ist seems that the kernel modules of the Intel graphics driver are loaded on these iMacs models too. But they are just used for AirPlay Mirroring and for Thunderboald connection and not for regular graphic displaying.

Most strange is the iMac10,1 since this CPU has no Intel graphic on the chip and is still Intel Core 2 Duo. But this user claims to have the problems since Mavericks 10.9 and so this is very probably a different issue(hardware issue?) since he is in this tread alone with that.

Unfortunately the people that have no issues with freezing since 10.11.4 are also never told us in detail witch hardware they use for having no issues. My guess is, that they have older hardware and these are models before 2015 and maybe they also have none of the suspect Intel graphic chip versions (Intel Iris Graphics 6100, Intel Iris Graphics 6000, Intel Iris Pro Graphics 6200 or Intel Iris Pro 5200).

Hello to everyone!

I have the same exact problem on my MacBook Air 13'' late 2015!

Here's the system log that I get when the freezing happens (I copied it from the Console after I restarted the machine):

05/05/16 18:23:55,046 Safari[345]: ERROR: History: Failed to insert item into the history_items table: UNIQUE constraint failed: history_items.url (19)

05/05/16 18:23:55,046 Safari[345]: ERROR: History: Failed to insert item into the history_items table: UNIQUE constraint failed: history_items.url (19)

05/05/16 18:23:59,975 com.apple.WebKit.WebContent[5205]: [18:23:59.975] FigFileForkOpenMainByCFURL signalled err=35 (errno) (open failed) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.20 2/Sources/Platform/Darwin/DarwinFile.c line 456

05/05/16 18:23:59,975 com.apple.WebKit.WebContent[5205]: [18:23:59.975] <<<< FigFile >>>> FigFileForkOpenMainByCFURL: opening url "file:///var/folders/76/t9wzpsq17fbc7_4yrvqz0pm40000gn/T//MediaCache/CachedMedi a-4EEz7G", path "/var/folders/76/t9wzpsq17fbc7_4yrvqz0pm40000gn/T//MediaCache/CachedMedia-4EEz7 G" options 0x00000480 failed errno 35 Resource temporarily unavailable

05/05/16 18:24:02,198 com.apple.WebKit.WebContent[5205]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 18601 took 1.100131 secs. to complete, 1 reads >= 1 sec.

05/05/16 18:24:03,356 com.apple.WebKit.WebContent[5205]: [18:24:03.356] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.202/Prototype s/LegibleOutput/FigAgglomerator.c line 92

05/05/16 18:24:03,366 com.apple.WebKit.WebContent[5205]: [18:24:03.366] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7ff9a128e800) rejecting report of layer being serviced - IQ has not yet begun to update

05/05/16 18:24:03,793 WindowServer[148]: _CGXRemoveWindowFromWindowMovementGroup: window 0x20 is not attached to window 0x2c

05/05/16 18:24:05,457 Safari[345]: tcp_connection_tls_session_error_callback_imp 94 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

05/05/16 18:24:18,430 Safari[345]: ERROR: History: Failed to insert item into the history_items table: UNIQUE constraint failed: history_items.url (19)

05/05/16 18:24:18,430 Safari[345]: ERROR: History: Failed to insert item into the history_items table: UNIQUE constraint failed: history_items.url (19)

05/05/16 18:24:18,450 Safari[345]: KeychainGetICDPStatus: keychain: -25300

05/05/16 18:24:18,450 Safari[345]: KeychainGetICDPStatus: status: off

05/05/16 18:24:31,959 Safari[345]: tcp_connection_destination_handle_tls_close_notify 89 closing socket due to TLS CLOSE_NOTIFY alert

05/05/16 18:24:31,960 Safari[345]: tcp_connection_tls_session_error_callback_imp 89 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32

05/05/16 18:24:31,960 Safari[345]: tcp_connection_destination_handle_tls_close_notify 90 closing socket due to TLS CLOSE_NOTIFY alert

05/05/16 18:24:31,961 Safari[345]: tcp_connection_tls_session_error_callback_imp 90 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32

05/05/16 18:24:31,962 Safari[345]: tcp_connection_destination_handle_tls_close_notify 93 closing socket due to TLS CLOSE_NOTIFY alert

05/05/16 18:24:31,962 Safari[345]: tcp_connection_tls_session_error_callback_imp 93 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32

05/05/16 18:24:46,401 watchdogd[317]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

05/05/16 18:24:47,409 watchdogd[317]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer)

05/05/16 18:25:11,470 watchdogd[317]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

05/05/16 18:25:12,473 watchdogd[317]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer)

05/05/16 18:25:36,000 bootlog[0]: BOOT_TIME 1462465536 0

My affected machine is a MacBook Air early 2015 7,2 with Intel HD Graphics 6000.

Do any of you get crashes when not using Safari and using Chrome instead? It's been 5 days for me since last freeze. If we all agree on this then it must be a simple driver conflict with safari.

Nice chart by the way. I have another iMac early 2009 on 10.11.4 which runs fine without freezing specs are:

Mac (20-inch, Early 2009)

2.66 GHz Intel Core 2 Duo

8 GB 1067 MHz DDR3

NVIDIA GeForce 9400 256 MB

The major difference here is the Nvidia GPU which does not cause the freeze in comparison to intel iris on MBP.

I own an iMac 21.5-inch, Mid 2010. I just checked my graphics card for you and it is the ATI Radeon HD 4670 256 MB. Memory: 12 GB 1333 MHz DDR3.

Again, since I upgraded my Adobe Flash Player, I have not had any freeze-ups. Naturally, because my computer is older, it is slower and sometimes I think it is going to freeze, but then it surprises me and doesn’t. I have no logical explanation for this.

P.S.: Great chart; thanks for posting it.

Edmundostudios wrote:

Do any of you get crashes when not using Safari and using Chrome instead? It's been 5 days for me since last freeze. If we all agree on this then it must be a simple driver conflict with safari.

I haven't had any crashes using Google Chrome yet! Just using Safari!