SecuritySpy 4 - heavy vtCompression and vtDecompression error logging
Found my mac shut down this morning for no apparent reason, so I started looking through the system logs. I don't know if it was related to SecuritySpy, but I found the logs with 100s error messages (see below) from the app.
Not sure what the issue is or if it is an issue at all other than heavy logging.
6/26/16 10:48:51.211 AM SecuritySpy[381]: [10:48:51.211] vtCompressionSessionTrackFrameGetInfo signalled err=-12902 (kVTParameterErr) (Unrecognised VTVideoEncoderFrame token passed in by encoder) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.204/Sources/VideoToolbox/VTCompressionSession.c line 2301
6/26/16 10:51:26.544 AM SecuritySpy[381]: [10:51:26.544] vtDecompressionDuctDecodeSingleFrame signalled err=-12909 (err) (VTVideoDecoderDecodeFrame returned error) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.204/Sources/VideoToolbox/VTDecompressionSession.c line 3486
Any thoughts/suggestions?
Thanks.
Eric
Not sure what the issue is or if it is an issue at all other than heavy logging.
6/26/16 10:48:51.211 AM SecuritySpy[381]: [10:48:51.211] vtCompressionSessionTrackFrameGetInfo signalled err=-12902 (kVTParameterErr) (Unrecognised VTVideoEncoderFrame token passed in by encoder) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.204/Sources/VideoToolbox/VTCompressionSession.c line 2301
6/26/16 10:51:26.544 AM SecuritySpy[381]: [10:51:26.544] vtDecompressionDuctDecodeSingleFrame signalled err=-12909 (err) (VTVideoDecoderDecodeFrame returned error) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.204/Sources/VideoToolbox/VTDecompressionSession.c line 3486
Any thoughts/suggestions?
Thanks.
Eric
Comments
-
Hi Eric,
How frequent are these messages? They indicate problems decoding the incoming video. When SecuritySpy encounters this it will simply skip the bad frames, unless there are many in a row, in which case it will display an error. If they are not too frequent then you can safely ignore them, but if they are happening a lot then this would certainly be more of a problem. -
Apologize for not responding sooner. I must have been having a network issue or some unrelated load on the Mac. The frequency on the day I reported was really high. Since upgrading to the 4.0.2 I have not notice the messages in the system log. However, I don't think the upgrade is related, the frequency had gone way down as well before the latest version.
