Apparently allocated by webkit for Javascipt-related functions.not abnormal by itself but double-check Activity Monitor CPU and Memory tabs. Large amount of virtual memory (not physical memory) allocated - 79 GB. (?) Just announced at WWDC as beta? Not sure what that means. Time since MacOS boot: 2 days 13 hr (suggest reboot). Below is all I can gather from the WebKit crash log: If those are not denoted in the previously-listed locations, the next time FCP crashes and raises a crash dialog, select all the text with CMD+A then paste it to TextEdit and save as a. It appears that crash log was not for FCP but for a Safari component called. Examining the crash log can help isolate that. I can examine it for clues.Įven though you've removed all plugins, it might be some kind residue from a buggy plugin. You can CMD+A to select all then paste that to a plain text file using TextEdit and attach it to a post - please do not post in line. Those are also available by running the Console app and selecting Crash Reports in the left sidebar. You can go there in Finder by holding the OPT key and clicking the Go>Library menu. The FCP crash logs should be in ~/Library/Logs/DiagnosticReports. Make sure all library and media files are on directly-attached drives formatted as either HFS+ (Mac OS Extended Journaled) or APFS. Run Activity Monitor and check the memory pressure graph under the Memory tab. However the part about having another app running is suspicious. Your description mostly indicates an application layer problem not system layer. IOW AJA or Blackmagic devices, wireless headphones, etc. If you have any external video or audio hardware (wireless or not) try disconnecting that. There have been many past problems traced to Chrome, and I don't know if those were ever fixed. Also, as a test do not run the Chrome browser. Make sure you have at least 20% free space on all drives. You may have already done this, but reboot the machine.

Imac keeps freezing 2017