I need to execute the following shell script in my macOS terminal. The loop never executes more than its first iteration. Function executefunction # Launch job numberofjobs=$1 echo 'Lau. Give the Partition a name, make sure the format is Mac OS Extended (Journaled) and click 'Apply'. If the Scheme is set to GUID Partition Map, skip to step 4. If not, click the Erase tab, change. Loopback gives you incredible control over how audio is routed between applications and devices on your Mac. With just a few clicks, you can easily pass audio. Mac OS X 10.10/10.11/10.9. Install Mac OS X Yosemite on VMware, and it is the 11th major release of Mac, Apple company. Therefore, this version of Mac OS X Yosemite is 10.10 and it was the old version of macOS operating system among the other operating systems. So here we are, at the end of OS X. Two decades ago Apple parked the sixteen-year-old Classic Mac OS and leaped to version 10.0, but four years ago the company rebranded the software that drives the Mac as macOS, and the writing was on the wall. And now in 2020 it’s macOS Big Sur, version 11.0.
|Click here to return to the 'Recover from a constantly restarting Finder loop' hint|
this usually has to do with a corrupt character that the finder cannot display in the desktop. for some reason it does not effect the finder when it is in a folder other than desktop. alot of times there will be a .textClipping file that is causing the constant crash loop, do you have one of those?
the other root of the problem is many times Fonts as well. have you removed some fonts from the /System/Library/Fonts folder? Some of the asian fonts are actually needed to prevent finder crashing when it encounters this bad character as well..
Note also i have had the same problem with corrupt dstore files, if anyone wants a copy of a corrupt dstore file? send us an email
You know, this exact thing happened to me a few days back. I had installed the newest version of DesInstaller (an uninstall program) and mistakenly removed the AsianCharacters.pkg (called something like that). I got the finder loop as soon as the uninstall was done. Restarting had no effect. Finally I booted from the system DVD and did an Archive and Install. Not sure if it was the package I removed or DesInstaller itself that caused the problem. Wish I had thought of the Path Finder thing. Ah well!
Hmmm. Wish I had read the other comment before posting. Lesson learned.
This bug can also happen if you have a corrupt application bundle, e.g. one with a damaged .plist file or icon. Apple could put some more work into making the Finder more robust in dealing with these sorts of things.
I see this problem a lot. As other posts have mentioned it's usually the fault of an evil .textclipping file sitting on the desktop. The problem is reproducible in Mail.app by dragging a word document attachment from an email to the desktop. Only seems to happen if the user has previously changed their default program for opening word files from MS office to TextEdit.
I always do a custom install of Mac OS X without the asian language support files to save HD space and these might be needed to display the text clipping on the desktop else the Finder crashes infinitely. It's a pain that the finder in 10.4.5 isn't more robust in this manner. If the user is a non admin user they are helpless to fix this.
Geneva.dfont4 - restart
To weird. Wish I had found this thread earlier. I just spent hours trying to find a cure for this ailment. I first thought it had to do with the new security update. Did all the usual.
Finally logging in as another user I just happenedd to look at my other desktop and saw this attachment I had dragged there earlier. Bingo.. file name and I too have removed asian fonts.
Doing the mv command robg recommends will not preserve all resource forks and metadata on the desktop, probably some users will not want to do that!
Instead using ditto and then removing the files with rm will be a better way to do it, if any metadata is to preserved.
Actually with OS X 10.4 Apple sadly modified common Unix tools such as cp, mv, tar, rsync to supprt resourse forks so it will retain the fork unless you set a flag to not do so unless you are on an older version of OS X of course then you will need ditto or cpmac.
Does anyone know if Apple are aware of this Finder problem? I don't have developer status or access to the radar system and have been waiting for a bugfix since 10.4.0. I'd rather avoid installing the Asian Fonts package to fix this as it will add 1Gb to my Apple System Restore build image. I also use Monolingual to remove unused languages to save space.
Cheers for any info.
Another reason for Finder crahsing constantly is a another damaged .plist. Had this problem on several Macs before. If this hint doesn't work, try to remove
To the fonts problem: I had so many problems with fonts removed by Users. It not only affects OS X itself, but also other programs if their fonts are removed. Filemaker 8, Office 2004 etc. tend to crash with debug entries (from crash-log) like
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x9073fba4 CFRetain + 60
1 com.apple.CoreText 0x90235b08 TFontCascade::InitParams() + 324
2 com.apple.CoreText 0x90235bac TFontCascade::CreateFallback(__CTFont const*, __CFString const*, CFRange) const + 52
If you see simular entries, check if all standard fonts are installed.
Awesome -- this just saved me hours of rebuilding that wouldn't have worked anyway if the user account was re-imported. The culprit was a file on the desktop named ???.textClipping . I suspect this appeared due to a failed/incomplete download, as it wasn't user-created. Since deleting it fixed the finder loop, it may be possible to re-create the problem (if one were so inclined) by creating such a file and rebooting or logging out.
Did what to post suggested but nothin doing, finder still crashes. Path Finder worked. The Finder only crashes when I move files over a gb. Any ideas? Thanks!
A Troubleshooting Protocol to Identify Problems or Fix macOS El Capitan or LaterOs x games.
You should try each, one at a time, then test to see if the problem is fixed before going on to the next.
Be sure to backup your files before proceeding if possible.
Mar 2, 2018 12:54 PM