Screensets implicates Crash

Hi miteinonda,
My screenset recall / copy / delete functions tend to crash Logic (estimated every 2nd function call). It is a long-term problem and I already forgot as I dont use them anymore. But every half a year I try to find a solution, and here I am-)
I start the commands either by key command or windows. The latest attempt was to use the key commands of the global System preferences (pref pane). Nothing works. Logic tries to save the song as a crashed file and quits.
Anyone an idea?
The installation of Logic seems ok. I had this problem also with Logic 8. And I'm working quite much with it and there is nearly never a crash not due to this screenset problem.
Thanks in adv and good luck to you all.
Message was edited by: jandu1

Yes this is a known problem - with Quicktime. Downgrading to QT 7.4.5 works for some.
http://discussions.apple.com/click.jspa?searchID=-1&messageID=9755619

Similar Messages

Why Does Logoc Pro (With Video Loaded) Crash When Changing Screensets?

Hi,
I have an annoying problem which has only started happening since I've been working in Logic Pro with a movie loaded.
The movie (.mov) is 2min 59 sec long and 3.2MB.
There are about 12 audio tracks with my voice commentary on them and I'm working on a music track to go behind video & voice.
My Mac OSX !0.5.7 has 7GB of RAM.
The crashes happen regularly but only when I change screen sets.
Thankfully the program saves my file every time but it is still annoying because I have to load up again.
I've also turned off automatic backups and a virus barrier but it does not help.
Has anybody had this problem?
any assistance is much appreciated.
thanks,
GB
PS: Since this movie project is my first, how do I save the movie with my voice commentary and music when I'm finished? Is it just a normal bounce?

Yes this is a known problem - with Quicktime. Downgrading to QT 7.4.5 works for some.
http://discussions.apple.com/click.jspa?searchID=-1&messageID=9755619

Logic Crash whe using Screenset with UAD Plugins

Hey
When switch between screen set logic sometime crash and it's alway using the UAD Neve 88R
I got the last driver from UAD and also the Last Apple update check all the right and smart with Onyx
and also restart my template from scratch incase it was corrupted or something but same thing
mmmmmm

Hi,
Firstly, are you on Mac OSX 10.4.10? Did you update via auto-update? This is broken since 10.4.9, and Apple has recommended one download the combo version of the updates.
Secondly, have you replaced the FireWire cable between the LaCie and the Mac? How fast is your LaCie (7200rpm is minimum recommended)
If your undo history includes a LOT of audio edits, this might be an issue. You can save your song as a new name, and dump the undo history, and see if this helps.
I do not think it is the audio cards, but maybe the UAD card. Make sure you have their latest software / firmware compatible with your Mac.
Cheers

Logic Pro 9.1.8 + Mountain Lion 10.8.2 - Frequently crashes when using plug-ins

I'm really hoping someone can help. I suspect this problem is new since I can't find a definitive answer.
When using the third party plug-in Superior Drummer 2, Logic Pro 9.1.8 frequently crashes giving problem report 'Logic Pro quit unexpectedly while using the Superior Drummer plug-in' followed by details.
This also happens when using Arturia Analog Laboratory. Similar problems have been reported by others using third party plug-ins.
Some have suggested removing the folder /System/Library/PrivateFrameworks/ProKit.framework and then installing ProKit Update 7. I've tried this without success. Once removed, attempting to install it only launches the alert 'a newer version of this software is already installed', which it patently isn't. Removing it also prevents Logic Pro from launching and requires the reinstallation of Mountain Lion.
Others say it's a problem with Mountain Lion and even Lion. Apparently, the above fix works with Snow Leopard but unfortunately, since I downloaded Snow Leopard from the app store, I can't revert back because it's no longer available.
I don't know whether the problem is with the plug-ins, Logic Pro, or the operating system but I do know that this is not uncommon. I haven't yet found anything to implicate the plug-ins. All have been updated to their latest versions. I can not verify whether the plug-ins worked in previous incarnations, with a previous operating system or Logic Pro since I've only ever used them with Mountain Lion on a MacBook Pro Retina 2.7 GHz Intel Core i7, 16 GB 1600 MHz DDR3.
The current cacophony of forum discussion is roughly sounding out Mountain Lion as being the issue.
I'm in the dark here! HELP!!!

The issue, according to other AAL users, is Arturia's drivers I am afraid to say.. The v1.5.2 ones work for some people but not others and they are waiting on a further update from Arturia to fix the issue. It isn't something that reinstalling ML or the Prokit for that matter.. fixes... unless you have some other issue with other plugins and software?

Video intermittently not going to Firewire DV output -- crashes too!

I have 2 very annoying issues with video in Logic. Video goes through firewire to a Canopus ADVP 300.
There's a 50/50 chance that on opening a session that the video will not show up on the screen but rather in the little video preview window on the upper left of the Arrange window. It requires double-clicking on the picture to send it out to the firewire. The video is saved and screenset-locked with the video going out the firewire. It's annoying!! Does anyone know what's going on??
Also, there are occasional crashes which seem to be due to video, judging by this:
Thread 0 Crashed:
0 com.apple.QD 0x9171ffa5 RGBForeColor + 57
1 com.apple.QuickTime 0x9434e0ea TaskMovie_priv + 2355
2 ...ickTimeComponents.component 0x98bfa6b7 doIdleMovie + 242
3 ...ickTimeComponents.component 0x98c08d88 internalDoAction + 2622
4 ...ickTimeComponents.component 0x98bfa536 _MCIdle + 41
5 ...ple.CoreServices.CarbonCore 0x90cd0b1b CallComponentFunctionCommon + 513
6 ...ickTimeComponents.component 0x98bf5a0f _MCComponentDispatch + 118
7 ...ple.CoreServices.CarbonCore 0x90cd0800 CallComponentDispatch + 34
8 com.apple.QuickTime 0x944378e6 MCIdle + 37
9 com.apple.QuickTime 0x944360f7 QTOMovieObject::SendCommand(unsigned long, void const*) + 313
10 com.apple.QuickTime 0x9433969c DispatchQTMsg(void const*, unsigned long, unsigned long, unsigned long, QTOGenericObject*) + 530
11 com.apple.QuickTime 0x943393bf QTObjectTokenPriv::SendMessageToObject(QTMessagePriv*, unsigned long) + 183
12 com.apple.QuickTime 0x943388cd QTObjectTokenPriv::DispatchMessage(QTMessagePriv*, void const*, __CFAllocator const*, unsigned long, unsigned long, ComponentMsgParam*, unsigned long, unsigned long) + 1321
13 com.apple.QuickTime 0x94435fb6 QTSendToObject + 98
14 com.apple.QTKit 0x9044cdab QTObjectTokenExecuteCommand + 82
15 com.apple.QTKit 0x9044c941 -[QTMovie idle] + 187
Any ideas about that?

You're not losing firewire control when you switch over, you are losing the video playback. Even if you were viewing your canvas on your desktop you would still go back to a ragular screen when you switch apps. You would probably have to monkey with your external monitor to adjust how it responds to a lack of signal.

InDesign keeps crashing on type tool/when multiple files are opened??

I've 'trashed' my preferences, updated both Suitcase 3 and CS5 to the latest updates...and still having issues. Just constant crashing whenever I open multiple files, or as soon as I enter a text box to make edits.
Here's my two crash reports:
pastebin.com/Q3LeHAZ7
http://pastebin.com/3pSxgUvN
And a sample process:
http://pastebin.com/DDCGyEG1
Any advice would be greatly appreciated! Thanks!

Hmm yes, I've just had my first crash of the day - tried to package a file and it froze when copying the font files over.
Well, that does seem a plausible summary of what is happening. Your crash report is of particular interest, because it doesn't really implicate InDesign:
Thread 34 Crashed:
0   com.apple.CoreFoundation           0x91f6f65f _CFURLIsFileURL + 15
1   com.apple.CoreFoundation           0x91fd2a80 CFURLSetResourcePropertiesForKeys + 32
2   com.apple.DesktopServices          0x90bc6af0 TCopyWriter::WriteDates() + 990
3   com.apple.DesktopServices          0x90bc639f TCopyWriter::WriteExtendedAttributes() + 357
4   com.apple.DesktopServices          0x90bc00f3 TCopyWriter::Write() + 185
5   com.apple.DesktopServices          0x90bbf9d5 TCopyWriter::WriteTaskProc(void*) + 75
6   ...ple.CoreServices.CarbonCore     0x9294254a PrivateMPEntryPoint + 68
7   libSystem.B.dylib                  0x90a06259 _pthread_start + 345
8   libSystem.B.dylib                  0x90a060de thread_start + 34
so, that is a crash in Apple code. Now, of course, the apple code was called from InDesign, and there's a certain degree of garbage-in-garbage-out. If you ask the operating system to copy a nonexistent file to a nonexistent device, it might crash. It shouldn't but it might.
And if we look at thread 0, which is InDesign code, we can sort of see where InDesign invoked the operating system:
Thread 0: Main Thread Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib                  0x90a06aa2 __semwait_signal + 10
1   libSystem.B.dylib                  0x90a0675e _pthread_cond_wait + 1191
2   libSystem.B.dylib                  0x90a083f8 pthread_cond_wait$UNIX2003 + 73
3   ...ple.CoreServices.CarbonCore     0x9297721e TSWaitOnCondition + 126
4   ...ple.CoreServices.CarbonCore     0x92962b68 TSWaitOnConditionTimedRelative + 202
5   ...ple.CoreServices.CarbonCore     0x9295e533 MPWaitOnQueue + 250
6   com.apple.DesktopServices          0x90bc730b TCopyQueue::WaitOnRecordDone() + 55
7   com.apple.DesktopServices          0x90bc1287 TCopyReader::GetNextItem() + 875
8   com.apple.DesktopServices          0x90bbfdf6 TCopyReader::Read(unsigned long long, TCountedPtr<TCFURLInfo> const&, TCountedPtr<TCFURLInfo> const&) + 164
9   com.apple.DesktopServices          0x90bf64e3 TFSCopyOperation::CopyToTarget() + 613
10 com.apple.DesktopServices          0x90bf9228 TFSCopyOperation::DoCopy(TCountedPtr<TCFURLInfo> const&) + 780
11 com.apple.DesktopServices          0x90bf9898 TFSCopyOperation::Run() + 174
12 com.apple.DesktopServices          0x90bee5e9 _NodeOperation + 438
13 ...ple.CoreServices.CarbonCore     0x929c2090 _FSOperateOnObjectSync + 352
14 ...ple.CoreServices.CarbonCore     0x929c228f _FSPathOperateOnObjectSync + 210
15 AdobeAFL                           0x016e9101 adobe::afl::CoreFileUtils::CopyFile(adobe::afl::AFile const&, adobe::afl::AFile const&, bool) + 365
16 PublicLib.dylib                    0x014339da FileLinkResourceHandler::CopyToFile(UIDRef const&, URI const&, IDFile&) const + 58
17 com.adobe.InDesign.Links           0x21c54c4e 0x21bd8000 + 511054
So, where does that leave us? Well, we would like to know what file is being copied, and why the file copy operation caused the operating system to crash the program.
Are you sure it was a font? Could it have been copying another linked file?
I don't suppose you have any folks around the office who know their way around Apple's Xcode tools, that are used for developing Objective C applications? There are some ways to figure out what file is causing InDesign to crash, but they're all kind of cryptic and annoying to explain without doing it in person...
If not, let me know and I'll try to figure out a simple way to explain it... (and to figure out which of the cryptic tools are the best ones to recommend for this situation. A question that might take me some time to answer....)

Premiere Pro Crashes when Nudging Clip

Premiere Pro is crashing (spinning pinwheel forever... go for lunch...45-60min, come back, force quite, "PPro has encountered a serious error") during simple tasks such as "nudging" a clip in the timeline or clicking with the "razor" tool. This is destroying my productivity, any help appreciated. This is hapening on 2 different machines linking to the same set of media. Full system details below.
All Media is ProRes422(LT) stored on a AFP share drive. Both systems are setup with media cache files on the local drive, Murcury Playback Engine (CUDA).
System 1:
System is running a fresh install of OS X 10.9.2 (as of Monday)
MacPro 5,1 dual 6-core 2.4GHz
48GB RAM
GTX570 2.5GB GPU (Driver: 8.24.9 310.40.25f01, CUDA: 5.5.47)
PPro CC 7.2.1(4)
Blackmagic Intensity Pro Card
Desktop Video 10.0
System 2:
iMac 13,2 i7 3.4GHz
OS X 10.9.2
16GB Ram
GTX 680MX 2GB (Driver: 8.24.9 310.40.25f01, CUDA: 5.5.47)
PPro CC 7.2.1(4)
Project files contain approx 13,000 assets and take upwards of 8 min to load all media.
Scott

Hi Scott. The reason I made those suggestions was because I had the same problem once. Nudging certain clips or moving audio keyframes resulted in an instant repeatable crash. This was because I imported the XML with audio automation from an FCP7 project. Stripping the audio keyframes cleared up the crashing issue. I just had to remix the whole short film. And Adobe also volunteered that they were seeing the same problems with stabilzation data.
I haven't seen much corruption on ProRes. My experience has mostly been with JPEGs and Long-GOP video.
I haven't done much cutting off a network; mostly just transcoding or exporting. But, no crashing ensued. However, you could rule that out by copying some of your footage locally, and see if you get the same crashing.
Before Corrupt Clip Finder, I had a "search and destroy" method for finding clip corruption. This goes back to my Avid days. The routine in the same: start isolating or taking half your media off line, and see if it still crashes. Keep taking footage off until the crashing stops. That tells you the corruption was in the last batch you took offline.
You can use the "Make Offline" feature in Pr without having to physically move anything. So, another thing you could try is to take all your media off line, and see if you get crashes by nudging clips. If so, that would implicate the project, and not the media.

Illustrator CC Touch Type Crash

Just downloaded a bunch of CC applications, including Illustrator.
Illustrator seems to work fine, but every time I try to select the Touch Type tool, the program crashes and quits.
I'm using OSX 10.8.4
Here is the crash log:
http://pastebin.com/T5JdBhj0
Tried resetting preferences, but there was no default available to reset them to. Also tried deleting the Adobe Illustrator Prefs files, but they don't exist on my computer...

But the crash implicates your Wacom tablet. Have you disbled the wacexport.aip file and tried it?
See here
http://forums.adobe.com/thread/1244304?tstart=0
and here for the hidden files
http://helpx.adobe.com/x-productkb/global/access-hidden-user-library-files.html

QuickTime 7.04-Pro crashes with almost every action

Hello MacFriends,
I have constant crashes while performing cut/copy/paste, dragging the slider, playing backwards (and forwards), fast-forward & backward, opening 2 files at the same time, playing single frames with the arrow-keys, switching to full-screen and back, etc., etc.. This happens while basically trying to search and copy/paste pieces from one .mov-file to another. Reverting to 6.5.2-pro solves the problems, but accurate copy/paste-actions are almost impossible in QT-6. (although the screensetting-options like brightness, contrast and color are back, I still don't understand why they left this out in QT-7) Trashing prefs, reinstalling, etc. don't help either.
I don't expect much performance from my 'old' imac, but I think this is quite a bit too much, certainly because QT-6 doesn't crash: It's just unusable at the moment.
Do I just have to wait for 7.1 or are there other options to solve these problems? And tips about using QT on a slower computer are also welcome.
Many thanks for your attention.

Thanks QuckTimeKirk, that really made a difference.
But where in my home-folder can this problem originate, since I have repeatedly thrashed all QT-stuff in ~/library as well in /Library? Can I solve this without having to bring everything over to a new account?
Thanks for your quick reply, it's good to know that QT-7 isn't too heavy for my machine and that a new user account did solve the problem.
Many regards,

LOGIC PRO 8 crashing when switching between screen sets

Hey eveyone -
first post up on this forum - but have been a professional logic user for years!
I like to think I am very well versed with the set up and running of mac systems and have come across a strange anomoly that i would appreciate if any one else out there has had happen - or would mind repeating - only takes 2 minute.
i have just bought a new mac pro and have logic pro 8 instaled and a variey of plugins
first
create a screen set & save as 1
create another with no movie as float and save it as 2
toggle backwards and forwards between them and notice you machine does not crash...
now ...
create a screen set & THIS TME OPEN A MOVIE AS FLOAT and saveit as part of your screen set - say to number 1
create another with no movie as float and save it as 2
now do the same thing and tell me if Logic crashes.....
mine does and it is bloody annoying as i compose to picture and need this to work smoothly.
I have unloaded all the plugins in the AU manager, tried putting the movie file on different drives, tried diferent movie files.... all the same.... I've tried it with other float windows and all works perfectly fine - so have narrowed it down to the movie float does not like being part of a screen set when you moving around between screensets frequently....
HELP!!!!!!! anyone out there have ideas??
really much appreciated any help anyone can shed on this or at least repeat the problem so I know it is a limitation of architecture not just my system....
many thanks
Paul

well guys - thanks for that - it would seem that after trashing my prefs file I reloaded the cue i was working on and did the swithing back and forth and that it still crashed the session.
I then tried it with a new song and with the same movie - and DIDNT crash -
so what I am think is this - i recently came from logic 7 to 8 and have transfereed my auto load from systen to the other.
I think it might be something in that
- i will check it
I think the answer might be to rebuild a new autoload within 8 - it's the only way to be sure...
...what do you both think??
and thanks again for your help - good to know there is someone out there when these strange things happen!!!
P

Where did 'saved a crashed version' go apple???

hello everyone.
i have to say, since ive been on snow leopard, intel machines and logic 8 and 9 logic and apple has seriously gone down in my estimation.
obviously its gone up in other ways but because of the amount of crashes and problems i get with logic and in general with everything else i just aint happy anymore.
i used to get crashed versions saved when logic fell flat on its face but for a long time i havent seen that message and i simply loose my work.
after a certain amount of work has been lost you truly start to question your future with your working method and have to re-evaluate and thats where i am right now.
i work a lot with ableton which also crashes as much as logic except it always restores my work to the last place i left off when i re-open it which is frikkkin amazing! its like a constant money back guarantee except you never need to take it back!
i wondered if there is any other folks out there that feel like i do right now and can offer any advice?
peace out!

Mike Connelly wrote:
Sometimes it saves a crashed version, sometimes not. Sometimes Logic locks up with spinning beachball of death and has to be force quit (yesterday force quit didn't even work and I had to reboot my machine from the power button).
Came across this and thought of this thread (thanks to: Logic Dudes http://logic.dudesnetwork.com/ ;
Force Project Save on Application Hang
by Matt on February 7th, 2010 in Advanced
Application crashes are inevitable. They will happen at one time or other and seem to strike at the most inconvenient of times. DAW apps can crash from bugs in their code or from bugs or issues with third party plugins. Sometimes, Logic is smart enough to detect a crash and save the current project as a “Project (crashed).logic” file. However, I have had Logic lock up but never completely crash on more than one occasion.
This happened to me today while working on a project. I tried to change to a screenset with a 3rd party plugin window open while the project was looping. Something caused Logic to lock up and display the spinning beach ball of death while the project continued to loop in the background. I couldn’t stop playback, change screensets, or save the project. I figured Logic would eventually crash and ask me to save, but 5 minutes later it was still going and I still couldn’t do anything. I looked at the timestamp of my project file to see when I last saved. Intstead of losing my last 10 minutes of work, I decided to figure out a way to make Logic crash and automatically dump the project. Simply selecting “Force Quit” was not an option because it doesn’t tell Logic to dump the project before quitting. After some quick testing on another machine, I found out that if you kill Logic via the terminal it will save the file as if it crashed as long as you send the correct kill signal.
Please note that this may not work in all situations.
Here’s how to do it.
Open Terminal.
Type ‘top’ and press enter. You will see a window like the one below.
Find the PID for Logic. In the screenshot above the PID is 8070. This number will change each time you launch Logic.
Press ‘q’ to get out of top.
Type the following command and press enter. Remember to replace XXXX with the correct PID.
kill -s ABRT XXXX
Logic should tell you that it crashed and has saved the project for you.
Hopefully, you can proceed to reopen Logic and load the (crashed).logic project file and hopefully recover your changes without Logic crashing again.
Performing the steps above will cause Logic to save a (crashed).logic project file even if it is not locked up. So, feel free to try it on an empty project for practice. That way you don’t mess it up if you have to use it on an important project!

Switching to Arrange view, Logic 8.0.2 keeps crashing

Hi,
I have a very annoying problem: I use Logic for film scoring. Since I updated to 8.0.2, Logic quits every time I switch from the video window to Arrange, which happens quite often. This makes any kind of serious work almost impossible. Does anyone here have the same problem and perhaps a solution?
Thanks,
R.

Yes, exactly!
Video screen is on 7 and Arrange on 1 - this switch crashes it.
8.0.1 doesn't, but then you get the annoying "My name is Logic 8.0.1 and I can't remember that you had a video screen on Screenset 7" syndrom. But still better than the crash.
Do you have a workaround?

Problem with threads, program always crash

new to threads, may be doing something COMPLETELY wrong. When I run the program I get a couple of NullPointerExceptions in Thread-0 and Thread-1. I'm confused because it screws up when I call size() for arrayList, and in the API size doesn't throw anything.
public class ProducerConsumerRunner
   public static void main(String args[])
      Queue q = new Queue(QUEUE_MAX_SIZE);
      ProducerRunnable producer = new ProducerRunnable(q, ITERATIONS);
      ConsumerRunnable consumer = new ConsumerRunnable(q, ITERATIONS);
      //works good up to here
      Thread t1 = new Thread(producer);
      Thread t2 = new Thread(consumer);
      t1.start();
      t2.start();
   private static int ITERATIONS = 50;
   private static int QUEUE_MAX_SIZE = 25;
import java.util.ArrayList;
import java.util.concurrent.locks.ReentrantLock;
public class Queue {
     public Queue(int maxSize)
          list = new ReentrantLock();
          underLimit = list.newCondition();
          MAX_SIZE = maxSize;
     public void add(String line)
          list.lock();
          try{
                       System.out.println("add method of Queue");
               while(record.size() >= MAX_SIZE){//things get screwed up when this condition is evaluated
                    //size method is crashing the program
                    System.out.println("2");
                    underLimit.await();
                    System.out.println("3");
               record.add(line);
          }catch(java.lang.InterruptedException e){
               System.out.println("await interupted: "+e.getMessage());
          }finally{
               list.unlock();
     public void remove(int line)
          list.lock();
          record.remove(line);
          list.unlock();
     public ArrayList<String> record;
     private final ReentrantLock list;
     private final java.util.concurrent.locks.Condition underLimit;
     private final int MAX_SIZE;
import java.util.Date;
public class ProducerRunnable implements Runnable{
     public ProducerRunnable(Queue q, int itterations)
          this.q = q;
          ITTERATIONS = itterations;
     public void run()
          String date;
          for(int i = 0; i<ITTERATIONS; i++)
               date = new Date().toString();
               q.add(date);//this is where it screws up
               System.out.println(date+" added");
               try{
               Thread.sleep(100);
               }catch(java.lang.InterruptedException e){
                    System.out.println("ProduccerRunnable's sleep was interupted");
     private final Queue q;
     private final int ITTERATIONS;
public class ConsumerRunnable implements Runnable{
     public ConsumerRunnable(Queue q, int itterations)
          this.q = q;
          ITTERATIONS = itterations;
     public void run()
          //Queue q = new Queue();
          int length;
          for(int i = 0; i<ITTERATIONS; i++)
               length = q.record.size();//things are getting screwed up here
               while(q.record.get(length) == null)
                    length--;
               System.out.println((String)q.record.get(length));
               q.remove(length);
               try{
               Thread.sleep(100);
               }catch(java.lang.InterruptedException e){
                    System.out.println("ConsumerRunnable's sleep was interupted");
     private final Queue q;
     private final int ITTERATIONS;
}

question:
this works right
     public void remove()
          list.lock();
          int line = 0;
          try{
               *while(record.size() < 1)*
                    range.await();
               record.remove(line);
               range.signalAll();
          }catch(java.lang.InterruptedException e){
               System.out.println("await interupted: "+e.getMessage());
          }finally{
               list.unlock();
     }this is deadlock
*int list = 0;*
*while((list = record.size)<1) was screwing things up because of the assignment*record is ArrayList of strings. when better to use Vector instead of ArrayList? i notice no differnce and i use threads
initially I thought record.size was being evaluated and before could be assigned to list, time slice ran out. this could not be case because I use ReentrantLock (list) to lock it.
Edited by: bean-planet on Apr 1, 2009 4:31 PM

Iphoto crashing after using mini-dvi to video adapter

Hi, IPhoto on my Macbook is crashing. I can open it, then as soon as I scroll down it locks up and I have to force quit.
This started happening right after I used a Mini-DVI to Video Adapter cable to hook my macbook up to my TV. The adapter/s-video connection worked and I was able to see the video on the tv. But iphoto immediately locked up the computer when I went to slide show and now it locks every time I open it.
Any ideas?
Thank you:)
Dorothy

It means that the issue resides in your existing Library.
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD

Help my safari doesnt open and gives me a crash report

help my safari doesn't open and gives me a crash report ever since i downloaded a file from the internet. I have a macbook air (early 2014) with running os x yosemite version 10.10.1

There is no need to download anything to solve this problem.
You may have installed the "Genieo" or "InstallMac" ad-injection malware. Follow the instructions on this Apple Support page to remove it.
Back up all data before making any changes.
Besides the files listed in the linked support article, you may also need to remove this file in the same way:
~/Library/LaunchAgents/com.genieo.completer.ltvbit.plist
If there are other items with a name that includes "Genieo" or "genieo" alongside any of those you find, remove them as well.
One of the steps in the article is to remove malicious Safari extensions. Do the equivalent in the Chrome and Firefox browsers, if you use either of those. If Safari crashes on launch, skip that step and come back to it after you've done everything else.
If you don't find any of the files or extensions listed, or if removing them doesn't stop the ad injection, then you may have one of the other kinds of adware covered by the support article. Follow the rest of the instructions in the article.
Make sure you don't repeat the mistake that led you to install the malware. Chances are you got it from an Internet cesspit such as "Softonic" or "CNET Download." Never visit either of those sites again. You might also have downloaded it from an ad in a page on some other site. The ad would probably have included a large green button labeled "Download" or "Download Now" in white letters. The button is designed to confuse people who intend to download something else on the same page. If you ever download a file that isn't obviously what you expected, delete it immediately.
In the Security & Privacy pane of System Preferences, select the General tab. The radio button marked Anywhere should not be selected. If it is, click the lock icon to unlock the settings, then select one of the other buttons. After that, don't ignore a warning that you are about to run or install an application from an unknown developer.
Still in System Preferences, open the App Store or Software Update pane and check the box marked
Install system data files and security updates
if it's not already checked.

Screensets implicates Crash

Similar Messages

Maybe you are looking for