shadowspawn Posted April 1, 2002 Report Share Posted April 1, 2002 I have been having problems with a crash in LaunchCFMApp. Initially I saw the problem three times in a row when trying to backup a particular volume on my home Mac. I would see LaunchCFMApp crash and the backup would stop. Disk Utility said the disk was fine. On my fourth try the backup ran ok. I also just had a similar crash log on my work Mac while trying to quit Retrospect after a day long stall. Anyone else seeing a LaunchCFMApp crash? Seen three times on dual 450 MHz G4 running Mac OS X 10.1.3, backing up local volumes to firewire VXA (the early model with the SCSI-firewire adaptor). Seen once on 466 MHz G4 running Mac OS X 10.1.3, backing up to SCSI VXA. Link to comment Share on other sites More sharing options...
hfalls Posted April 1, 2002 Report Share Posted April 1, 2002 LaunchCFMapps is Mac OS X's way to launch Carbon CFM (code fragment manager) applications and I believe that many Carbon apps are launched this way so I don't think it means much on its own. Link to comment Share on other sites More sharing options...
CallMeDave Posted April 1, 2002 Report Share Posted April 1, 2002 hfalls is correct; LaunchCFMApp is used by many applications, including Retrospect. Have you noted what other applications are running when this happens? Perhaps Retrospect has an issue when it attempts to scan/copy files being used by some other open application? Link to comment Share on other sites More sharing options...
shadowspawn Posted April 2, 2002 Author Report Share Posted April 2, 2002 I did not have any other (visible) applications running, however it was my Mac OS 9 volume and maybe I inadvertently had Classic running. I'll experiment further. Thanks for the comments. Link to comment Share on other sites More sharing options...
shadowspawn Posted April 10, 2002 Author Report Share Posted April 10, 2002 I narrowed down my crash to backing up one particular volume. Following a tip on another thread, I looked for long folder names. I had one folder with a 36 character name. Shortening the folder name to under 32 characters seems to have fixed a repeatable crash. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.