Non-user-facing processes such as Spotlight indexing or file defragmenting might be encountering these files, and discovering the same errors that surface during file-copy operations, with the result being that the system hangs without any user-visible or user-initiated cause. It is conceivable these files became corrupted during normal system defragmenting when I first encountered these system hangs, I toggled the power on more than one occasion to force a reboot. These files may have fragments scattered, in bits and pieces, all over the drive. This incompleteness or minor corruption might be unnoticeable to the user or to most apps, but some process in Finder (or APFS) may consider the corruption irreconcilable. Some particularly large files might be nominally incomplete or mildly corrupted. Most of the fusion drive is occupied by data.Most of the fusion drive is rotational media, and therefore slower, relative to SSD.Spotlight goes read/write crazy on any new system install, entirely rebuilding its index. Clearly the files in question do, indeed, have problems, and something involved in file I/O cannot work past them. Initially, I just tried re-copying the file, but Finder consistently bogged, halted, and threw the (-36), at the same number of reported MB copied, each time. Thereafter I could locate the file in Finder, select it, and trash it. (Error code -36)” Ĭlicking OK cleared the error dialog, but it was usually upwards of half a minute before the beachballing stopped. “The Finder can’t complete the operation because some data in ‘the name of the file being copied’ can’t be read or written. While that happened, all open apps began beachballing. Mostly, these files copied without incident, but occasionally, the copy operation would slow to a crawl, then grind to a halt for anywhere from 15 seconds to a minute or more. I have about 110 GB of ripped DVD files originally intended for my media server, which could be copied and purged to free up space. Large files, which existed on this volume prior to the install, ground to a halt when being copied from the internal HD to an external USB-connected hard drive, and to networked volumes. This did not correct the system hangs, but it made them less frequent. One thing that did help was disabling Spotlight indexing for the entire volume. There were no instances of mdworker running in Activity Monitor while in safe mode. Rebuilding file/folder permissions in Home folder, and at the root volume level.īeachballing still occurred in safe mode, but its frequency was noticeably reduced. Copy operations on large files sometimes bogs, then freezes, and throws (-36) errors.User commands are queued, and acted on after the hang clears so normal commands to switch desktops (as an example) execute in series after the hang is cleared.Force-quitting or getting system info on them is not possible Activity Monitor’s capability to respond to user commands is just as hosed as everything else. Activity Monitor only reports the beachballed apps as “Not responding”.There is no indication in Activity Monitor of any background process that has run away with the processors, or swamped memory.Ctrl/right-clicking results in no popup menus, even where they’re expected.Clicking a stack in the Dock doesn’t result in the stack opening.The tags which typically appear over hovered items in the Dock are slow to respond, or nonexistent.Any new app will not launch until the hang is cleared.Switching to Mission Control does not work.If it does, the system remains unresponsive on the new desktop until the hang clears. Switching to another desktop rarely works.Windows are draggable and refresh as expected while being dragged, but none of their contents respond to user commands (scrollbars are nonresponsive, clicking selectable items results in no state change, etc.) until after the hang clears.(I do not run anything in fullscreen mode, so I have no idea if task switching in fullscreen works or not.) Switching to different open app windows works, but any open window remains nonresponsive until the system hang clears.This happens whether there’s a lot of RAM available (50%+), or very little (a few hundred MB). System install on Mac Mini (late 2012), 1TB rotational + 128GB SSD fusion drive. I’ve been closely watching this behavior, with the result that I’ve been able to reliably reproduce a system hang, make some surmises regarding the cause - at least in my case - and come up with a few suggestions that might work around the problem. Like (too) many others, I’ve discovered Mojave to be a source of exasperation, particularly because it seems to lock up periodically, sometimes for minutes at a time, with no identifiable cause.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |