One of the Console reports here at macrumors.com, had this gem:
04/04/16 15:32:50,638 com.apple.WebKit.WebContent[7769]: <<<< VT-DS >>>> VTDecompressionSessionWaitForAsynchronousFrames: WARNING: waited 10 seconds for video decoder to complete asynchronous frames; maybe it is stuck or has a buggy path that does not complete a frame?
Possibly a related (Oct 26, 2015)
report at an Apple Discussion (scroll down to forum member "Pressluft"):
[Pressluft] "I'm streaming a bought video from iCloud and sometimes the movie is freezing and then this message pops up in the console."
26.10.15 11:30:36,550 iTunes[484]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 56858 bytes @ 967131672 took 0.966991 sec. to complete, 19 reads >= 0.5 sec.
[Pressluft] "Then it takes around a minute then the traffics spikes up to 10Mbyte/s and the movie goes on."
I've looked over the many posts re El Capitan freezes, including all the Console (log) reports. I'm not an Apple Developer, nor expert.
The El Capitan freeze problem appears to probably be common among these:
- WebKit (component of, or used by, various Internet browsers and other applications)
- network connection (between a variety of nodes; also, AirPlay, iCloud, Internet, Wi-Fi)
- FigByteStream (secured stream byte [distribution?] difficulties and/or errors)
- stream data-compression / stream data-decompression
- stream data-encoding / stream data-decoding
- stream data-encryption / stream data-decryption
- codec troubles
It's not a hardware problem, though both hardware weaknesses and strengths may contribute ultimately to freezes.
Time constraints / time frames involved, for sending / receiving, for encoding / decoding, for encrypting / decrypting, and for compressing / de-compressing . . . data streams, have expectations, but can stumble over mixed bags of hardware-and-software combinations/configurations -and-setups.
The data-stream-connection/communication-processing seems to be getting jammed / stuck in exuberant/failed processing, causing CPU rates to rise and max-out, and some of the computers seem to be taking abrupt measures to bring the heat of all that, down, including freezing *you* (the user) out of activity.
Some computers might get cool enough, that they release control back to you, but others (particularly fanless) remain stuck.
I use
Marcel Bresink's utility:
for monitoring temperatures.
I expect that the freeze problem may make more clear, that a few computers do have some kind of hardware problem(s) that become(s) more apparent.
Otherwise, the freeze problem is a data-communications turmoil that escalates to some panic level(s) that causes the Mac to reduce both heat and the roar of it all.
I use
Northern Softworks (Lion | Mavericks | Yosemite | El Capitan) Cache Cleaner, in order to clean out the caches:
Cache Cleaning
Deep Cleaning
Clean Local Cache
Clean System Cache
Clean All Users Caches
before updating the OS. This utility's activity causes a Restart, after which I run Repair Disk Permissions (Disk Utility) and then Restart again. I try to reduce the Mac's business to a peaceful state, before updating/upgrading.
I mention Cache Cleaner because some of the Console log reports point to some cache items, and it may be possible, that Northern Softworks' Cache Cleaning might help? (
Safe Mode boot clears some of the cache items - such as "font caches, Kernel cache and other system cache files.")
Some Console tips. You can create your own log querys - New System Log Query - under the Console File menu.
An example of one that I've found handy:
[New] System Log Query window
Search name: LOWDISK (you can make that any name that you want)
Find messages where all these conditions are true:
Message contains LOWDISK
or, find messages where all these conditions are true:
Sender contains KernelEventAgent
or, find messages where all these conditions are true:
Sender contains hdiejectd
or, find messages where all these conditions are true:
Message contains Low Disk
or, find messages where all these conditions are true:
Message contains danger
or, find messages where all these conditions are true:
Message contains I/O Error
LOWDISK will show results when you install some programs such as Adobe Flash Player. Don't let those bother you. But you do want to pay attention, because other LOWDISK reports might mean a troubled disk drive (I/O Error - recurring).
These System Log Querys may help you organize what you see in the Console. It helps you to concentrate/collect specific log reports, for your consideration/review.
You might want to create another System Log Query for the El Capitan freeze problem:
[New] System Log Query window
Search name: FREEZE
Find messages where all these conditions are true:
Message contains FigByteStream
or, find messages where all these conditions are true:
Message contains FigAudioQueue
or, find messages where all these conditions are true:
Message contains FigRenderPipeline
or, find messages where all these conditions are true:
Message contains figPlaybackBoss
or, find messages where all these conditions are true:
Message contains FigAgglomerator
or, find messages where all these conditions are true:
Message contains FigAsset
or, find messages where all these conditions are true:
Message contains FigFile
or, find messages where all these conditions are true:
Message contains VTDecompressionSession
or, find messages where all these conditions are true:
Message contains vtDecompressionDuctCreate
Message contains signalled err
or, find messages where all these conditions are true:
Sender contains WebKit
Message contains signalled err
or, find messages where all these conditions are true:
Sender contains WebKit
Message contains is stuck
or, find messages where all these conditions are true:
Message contains video decod (leave as is - no trailing "e")
Sender contains WebKit
or, find messages where all these conditions are true:
Message contains coder
Message contains com.apple.xbs
Message contains Core
or, find messages where all these conditions are true:
Message contains tcp_connection_tls_session_error
or, find messages where all these conditions are true:
Sender contains com.apple.xpc.launchd
Message contains key does not do anything
or, find messages where all these conditions are true:
Sender contains com.apple.xpc.launchd
Message contains unknown key for string
or, find messages where all these conditions are true:
Sender contains com.apple.xpc.launchd
Message contains key is no longer respected
or, find messages where all these conditions are true:
Sender contains com.apple.xpc.launchd
Message contains key is only available
or, find messages where all these conditions are true:
Sender contains com.apple.xpc.launchd
Message contains error = (include that equals symbol)
or, find messages where all these conditions are true:
Sender contains spindump
or, find messages where all these conditions are true:
Message contains Invalid connection
Message contains com.apple.core
or, find messages where all these conditions are true:
Message contains com.apple.WindowServer
Message contains unresponsive
or, find messages where all these conditions are true:
Message contains go low power
or, find messages where all these conditions are true:
Sender contains kernel
Message contains reset
Message contains hang
or, find messages where all these conditions are true:
Message contains spindump
Message contains failed
or, find messages where all these conditions are true:
Message contains MediaValidator
Message contains codec
Message contains Unrecognized
or, find messages where all these conditions are true:
Message contains WebKit
Message contains Decode
Message contains codec
Using the System Log Query feature, may also help you to upload concise log reports to forums.
I have not posted to this forum in many years; it was older and worked a bit different; so, apologies if this does not appear as it should.
I agree that Apple has not been thorough at the work of making a more durable and stable Mac OS (and other Apple Mac applications).