Beash ball woes revisited

Friends, I'm really suprised that I haven't had any replies to my post. I guess that this means that I've already done what everyone might suggest, or perhaps I should have posted in the Mini forvm.
If any of you have some thoughts or suggestions for me, I'd really appreciate your help.
Jon
Friends, for the past few days, I've been getting the old beach ball, primarily in Safari and Mail - the apps I use the most. My mini acts like it is not accepting mouse input as there is often a lag before the click is processed. This is where I'm seeing the beach ball spin This is a new development. The mini has been been trouble free for two years and I've rarely seen the beach ball.
Here's what I've done to attempt to remedy this situation;
Run all of the Cocktail utilities several times. (permissions, logs etc)
Checked the disk with disk utility. No problems found. Ran repair anyway.
Run the Apple Hardware test. No problems found.
Dumped the autofill info in Safari.
Dumped the Safari and Mail Plists.
Downloaded and reinstalled the Tiger 10.4.8 upgrade
reloaded the system from the install disk. This made the most difference. I did NOT do a clean install.
Downloaded all of the upgrades that I needed after the system install. Things got worse. This morning after all of the upgrades were loaded, the beach ball is back with a vengence. Strangely enough, I don't see much, if any, of the beach ball action when I'm using FireFox, but I DO see it in most other apps.
It sure looks like something that I upgraded last night is the culprit, so
I dumped the Quicktime plist. No help.
I looked at Java this morning. It appears that there is a version of the upgrade that will kick java to 1.5. I'm downloading it as we speak.
Short of a reformat and clean install, I don't know what more to do. I'm hesitant to do the clean install just because the dirty install I did seemed to help so much. I really don't want to chase my tail much more.
I'll sure apprecitate your suggestions!
Thanks,
Jon
G4 Mini 1.25/512 Mac OS X (10.4.8)

You might check the Activity Monitor to see what is hogging your CPU time and/or Real Memory.
Be sure to select "All Processes"
We have an old iMac that that was infected by a similar malady, it appeared to be due to some daemon that was running. The daemon did not show up on any of our other Macs (4 in all), and we were unable to locate the offending executable on the Mac
Our final solution was to do a clean install of the OS.

Similar Messages

Spinning beach ball woes on 27 inch iMac

We have a mid 2010 27 inch iMac (and also a late 2010 13 inch MacBook Air, from which I am writing this post). About 6 months ago it was starting to get spinning beach balls, which I attributed to not having updated the OS (then 10.7). Having upgraded the Air to Mavericks with success, I also upgraded the iMac to Mavericks, and the beach balls got much, much worse, rendering the thing nearly unusable. I cannot for the life of me figure out what the issue is, particularly because the Air, which is about the same vintage, is working great under the same setup. Can someone who has not been staring at this problem for 6 months help?
Here's what I've got:
As I mentioned, mid 2010 27-inch iMac, 1TB hard drive, about half-full, backing up to a 2 TB Time Capsule.
We have two wifi networks to cover the whole house; one is integrated with the cable company's provided router and sits in the basement, and the other is the Time Capsule hooked up to the cable company's VoIP router upstairs. Because you cannot use the Time Capsule to extend an existing network if it is not an Apple network, I resorted to setting each wifi network up independently (separately connected to ethernet). My Air navigates this just fine, as do our iPads/iPhones, and I don't notice a speed difference between the two networks (assuming I have equally good reception wherever I am).
Notably, the Time Capsule seems to randomly stop broadcasting wifi every now and then (at intervals of a few days to a couple weeks), which requires a restart to get it working again. (This could be totally unrelated.)
The iMac was at 10.7 when the beach balls started; upgrading to Mavericks made the slowness/beachballs worse. As I noted, Mavericks did not cause any trouble with the Air.
The beach balls seem to coincide with a complete stall in everything the computer is doing. After the stall ends, the computer can be fairly speedy, so it's as if it pauses for several seconds to a minute or so to think very hard, and then goes back to its business.
There is usually a slight improvement if I shut down and boot up again, but it gums up pretty quickly.
Here's what I've done:
Started with 4GB RAM; added another 8 (total 12) after this all started. Equally bad before and after.
Stared at Activity Monitor and Console for long periods of time while watching for beach balls to try to detect a pattern.
In Activity Monitor, memory pressure is fine (esp. now that I added 8 GB), no swap used. The two worst offenders under CPU usage seem to be kernel_task or WindowServer, but they are not always monopolizing the CPU at the times when it is stalled.
In Console, the main two patterns seemed to be a frequent WindowServer "updates forcibly disabled" error, and what seemed like a constant browsing for wifi connections even though the computer was already connected to wifi. However, I couldn't figure out what either of these meant or what might be done to fix them.
Used disk utility, repaired permissions, verified disk, etc. - everything was ok, although some permissions were repaired.
Used third-party utilities, Onyx and iDefrag, to try to verify disk and clean things up. No significant problems detected, and no improvement.
Various other methods of cleaning up -- eliminating old software or files that aren't being used, emptying trash, taking extra files off the desktop, etc. In particular, having read that Mail might have issues handling Google accounts, I eliminated a heavily-used Google account from Mail and got a separate, lighter-weight third-party app to handle that account. That did seem improve things at first, but we seem to be back to slowness and beach balls again.
Final, last-ditch effort: backed up and then erased hard drive and (after another Disk Utility verify - still fine) did a clean install of Mavericks.
It took several attempts to download the installer using the Time Capsule network (kept stalling); switched to the other (non-Apple) wifi network and it downloaded and installed fine.
However, after the clean install, although it was not nearly as slow as before, amazingly, I still had spinning beach balls and hanging without having installed anything other than the OS.
I made several attempts to get into the backup to selectively reinstall files. Could not mount backup using Time Capsule -- option-clicking and selecting "Browse Other Backups" did not actually get me to the other backup. Using Migration Assistant, could not get the backup to load, or the loading was taking an inordinately long period of time, so I gave up. (Also, every time I tried to quit Migration Assistant to try to discover the problem with the backup loading, it hung and I had to hard-restart.)
So, since the clean install did not seem to fix the problem, and I was starting to worry about not being able to get to my backup, I have gone back to just restoring from the Time Capsule. It's telling me this will take over 200 hours.
The one thing I haven't tried is shutting down the computer, lugging it upstairs, and connecting it to Time Capsule via ethernet, at least for the restoration. I will do this if I leave the computer overnight and it's still not done in the morning.
I've done much searching of these discussion boards, and tried everything that seemed like a possible culprit. What am I missing? (Other than ditching this computer and buying a different one?)

We have a mid 2010 27 inch iMac (and also a late 2010 13 inch MacBook Air, from which I am writing this post). About 6 months ago it was starting to get spinning beach balls, which I attributed to not having updated the OS (then 10.7). Having upgraded the Air to Mavericks with success, I also upgraded the iMac to Mavericks, and the beach balls got much, much worse, rendering the thing nearly unusable. I cannot for the life of me figure out what the issue is, particularly because the Air, which is about the same vintage, is working great under the same setup. Can someone who has not been staring at this problem for 6 months help?
Here's what I've got:
As I mentioned, mid 2010 27-inch iMac, 1TB hard drive, about half-full, backing up to a 2 TB Time Capsule.
We have two wifi networks to cover the whole house; one is integrated with the cable company's provided router and sits in the basement, and the other is the Time Capsule hooked up to the cable company's VoIP router upstairs. Because you cannot use the Time Capsule to extend an existing network if it is not an Apple network, I resorted to setting each wifi network up independently (separately connected to ethernet). My Air navigates this just fine, as do our iPads/iPhones, and I don't notice a speed difference between the two networks (assuming I have equally good reception wherever I am).
Notably, the Time Capsule seems to randomly stop broadcasting wifi every now and then (at intervals of a few days to a couple weeks), which requires a restart to get it working again. (This could be totally unrelated.)
The iMac was at 10.7 when the beach balls started; upgrading to Mavericks made the slowness/beachballs worse. As I noted, Mavericks did not cause any trouble with the Air.
The beach balls seem to coincide with a complete stall in everything the computer is doing. After the stall ends, the computer can be fairly speedy, so it's as if it pauses for several seconds to a minute or so to think very hard, and then goes back to its business.
There is usually a slight improvement if I shut down and boot up again, but it gums up pretty quickly.
Here's what I've done:
Started with 4GB RAM; added another 8 (total 12) after this all started. Equally bad before and after.
Stared at Activity Monitor and Console for long periods of time while watching for beach balls to try to detect a pattern.
In Activity Monitor, memory pressure is fine (esp. now that I added 8 GB), no swap used. The two worst offenders under CPU usage seem to be kernel_task or WindowServer, but they are not always monopolizing the CPU at the times when it is stalled.
In Console, the main two patterns seemed to be a frequent WindowServer "updates forcibly disabled" error, and what seemed like a constant browsing for wifi connections even though the computer was already connected to wifi. However, I couldn't figure out what either of these meant or what might be done to fix them.
Used disk utility, repaired permissions, verified disk, etc. - everything was ok, although some permissions were repaired.
Used third-party utilities, Onyx and iDefrag, to try to verify disk and clean things up. No significant problems detected, and no improvement.
Various other methods of cleaning up -- eliminating old software or files that aren't being used, emptying trash, taking extra files off the desktop, etc. In particular, having read that Mail might have issues handling Google accounts, I eliminated a heavily-used Google account from Mail and got a separate, lighter-weight third-party app to handle that account. That did seem improve things at first, but we seem to be back to slowness and beach balls again.
Final, last-ditch effort: backed up and then erased hard drive and (after another Disk Utility verify - still fine) did a clean install of Mavericks.
It took several attempts to download the installer using the Time Capsule network (kept stalling); switched to the other (non-Apple) wifi network and it downloaded and installed fine.
However, after the clean install, although it was not nearly as slow as before, amazingly, I still had spinning beach balls and hanging without having installed anything other than the OS.
I made several attempts to get into the backup to selectively reinstall files. Could not mount backup using Time Capsule -- option-clicking and selecting "Browse Other Backups" did not actually get me to the other backup. Using Migration Assistant, could not get the backup to load, or the loading was taking an inordinately long period of time, so I gave up. (Also, every time I tried to quit Migration Assistant to try to discover the problem with the backup loading, it hung and I had to hard-restart.)
So, since the clean install did not seem to fix the problem, and I was starting to worry about not being able to get to my backup, I have gone back to just restoring from the Time Capsule. It's telling me this will take over 200 hours.
The one thing I haven't tried is shutting down the computer, lugging it upstairs, and connecting it to Time Capsule via ethernet, at least for the restoration. I will do this if I leave the computer overnight and it's still not done in the morning.
I've done much searching of these discussion boards, and tried everything that seemed like a possible culprit. What am I missing? (Other than ditching this computer and buying a different one?)

Continual Mac woes (no question, just a rant)

It's Tuesday, and I am having terrible problems with my Mac. But then, why should Tuesday be different from any other day of the week.
Here is a typical day for me. The computer appears to be working OK. I need to watch a DVD for my work. I turn on DVD player, and put one in. The machine can't read the disc. It clicks and whirls, but the icon does not show up on the desktop. Meanwhile, so distressed is the machine that it freaks out. What was up until now was a fluidly operating machine suddenly reverts back to its old ways (i.e., its ways of two days ago). The hold ups and spinning pinwheels begin to eat of hours of my work day. (Remember the old days when computers made life easier?) The machine becomes sticky, gummy. Oh, I can move the curser and it seems to work for a second but then gets stuck in the dock, which explodes in icons and then freezes for five minutes. Yes. Five minutes.
Would love to use Force Quit, but the cursor is spinning, and nothing is responding. Funny about that old Mac. You can't force quit Force Quit. I guess I need to leave it open all the time.
Of course, FQ usually works on Safari. I have never just "quit" Safari. It always requires Force Quit, otherwise I can't turn off my computer. It stalls shut down.
Now I have a DVD trapped in there and can't get it out. [But I just got an answer from another posting.]
In the old macs, there used to be a pin hole you could stick a needle into ... can't find one on my flatpanel iMac.
I bought my Apple flat panel iMac in August of 2002. Yes, I know that that is a long time to have a computer, but I am not rich nor attached to a corporation that can splurge on computers. The first weekend I had the machine, I had three kernal panics.
Among the other problems I have documented are the following: the dock hiding itself unbidden and other features checking and unchecking themselves (Aug 2002); bus errors connected with OS 9 (Sept); some problems that inspired the tech person (Eric)) to talk me through deleting my user i.d., resulting in the loss of two months worth of e-mail (Thursday, 12 September); Preview problems (September); a bizarre box with an unmovable and undeletable red stop sign in it that no tech person or other Mac user I know had ever hear of (Monday 30 September); printing problems; computer won't shut down, numerous disconnection errors, which turned out to be caused by an OS X update (beginning December, 2002, or later); Kernel panics (Feb); computer won't shut down (March); Faxstexx problems, program won't allow me to set it up, finally just deleted the software (April); keys like "V" freeze and repeat endlessly (May 21); DVD Player freezes (May); Safari and Mail begin quitting unexpectedly (May); cursor begins to blink and fade out, plus odd sounds come out of the speakers, a constant error beeping (Sept 9); DVD Player problems (Oct 4).
I called AppleCare while I had it about once a week (the total between August 2002 and the time it ran out was about 155 calls). Naturally, some of these calls are motivated by user error. On the other hand, many of the issues I have called about were unprecedented as far as the Tech person was concerned, such as the blinking mouse, the red stop sign, and the DVD Player woes.
Things improved with Panther, but in Tiger many of the same old issues have returned.
I have been having so many problems with my Mac that I once wrote a letter to the company asking when do I qualify for a new replacement machine. I never received an answer, but I felt better for about a day. Then I turned on my Mac again.

The spinning ball of death as we used to call it is often caused by a lack of RAM, it is hard to be sure as I am not working on your machine, but sometimes things can be improved with additional RAM, it makes it seem like a whole new computer.
A lot of your problems sound like stuff that can be fixed easily enough, and although frustrating things happen here and there with updates. It sounds like you are in fairly good spirits with it all, I would suggest just researching a bit more into maintenance you can do to help maintain the computer and educate yourself a bit more (sounds like you already have learned quite a bit along the way) and you will find a lot of these issues take you a few seconds to rid yourself of. I would start by making sure you are repairing permissions regularly and running the most up to date software. If a lot of problems persist, try creating a second user that is a "test" user to see if the problem is replicated on that user (don't delete your other one, but if you do find the problem not on the other user, you might have a corrupt user, however you don't have to lose all your emails there are plenty of ways to back it up and import it in, or even just bring the entire Mail folder from your library over to the new user). Another thing you can do if you find a lot of system problems is archive and install the OS, it takes a bit of time, but doing it overnight shouldn't be an issue, and you won't lose any of your stuff.

ICal woes - any help please

Hi everyone, I am having some major iCal woes that I hope someone has the answer to.
Ok this is how I handle my workflow. I have numerous calendars such as "call", "viewing", "meeting", "work misc", "personal" etc. All colour coded and I use the month view as standard.
Under SL I would double click the day I add an event go through the boxes (name, location, time, etc) click save and job done.
Now under Lion when I double click a day I get an event box but only the header. So I have to type the header hit return then double click on the event again to get the box up so I can assign the event the right time and calendar to use. This is taking twice as long as it did before under SL and is a pain when you have a client on the phone. Am I missing something here? Why is it now so hard? - and I have tried that quick entry business but it doesn't work for me, I simply want the whole calendar entry box when I double click in month view.
Next problem is all new events go in as a all day event. Again another click I didn't need to do in SL. Then untick all day and enter a time LionCal doesn't set the end time 1 hour later anymore it sets it hours later for me, sometimes into the next day so I have to click into the date box and type the end date, again a massive slow down in my workflow.
Finally and most annoyingly in month view I cannot for the life of me get a 12 hour clock with AM/PM. I checked my international page in sys prefs and all is ok but LionCal is not playing ball.
Any help would be appreciated as I love iCal and run my life with it over MobileMe.

If you want to Commit changes at every record level in a Multi-Record Block, you may have to write the following triggers at the block level :-
1) Key-Down
2) Key-Up
3) You will also have to handle Mouse Events
i.e When-Mosue-Click etc
In each of these triggers, issue a commit statement :-
i.e.
Trigger Name :- KEY-DOWN [ Defined at Block Level ]
Trigger Code
Commit_Form;
Next_Record;
The Commit_Form statement will display a message for the user to COMMIT transaction to the DB.
Shailender

Lock ups, beach balling 13" MBP

I go a new 13 inch MBP. Sometimes it locks up and i get the spinning beach ball for 10/15 seconds.
Anybody else with this problem??
Thanks

There is already an insanely long thread on this topic... Take a look here:
http://discussions.apple.com/thread.jspa?threadID=2054387&start=0&tstart=0

Possibility of drawing numbers on java bouncing balls?

Can anyone show me how to put numbers on these moving balls in my code. I need the numbers 1-60 on them. I have two sets the red and white. Here is my code. Any help is appreciated. I am trying to write a program to represent the powerball.
import java.awt.*;
import java.applet.*;
import java.util.*;
import javax.swing.*;
import java.awt.Rectangle;
class CollideBall{
int width, height;
public static final int diameter=20;
//coordinates and value of increment
double x, y, xinc, yinc, coll_x, coll_y;
boolean collide;
Color color;
Graphics g;
Rectangle r;
//the constructor
public CollideBall(int w, int h, int x, int y, double xinc, double yinc, Color c){
width=w;
height=h;
this.x=x;
this.y=y;
this.xinc=xinc;
this.yinc=yinc;
color=c;
r=new Rectangle(150,80,130,90);
public double getCenterX() {return x+diameter/2;}
public double getCenterY() {return y+diameter/2;}
public void alterRect(int x, int y, int w, int h){
r.setLocation(x,y);
r.setSize(w,h);
public void move(){
if (collide){
double xvect=coll_x-getCenterX();
double yvect=coll_y-getCenterY();
if((xinc>0 && xvect>0) || (xinc<0 && xvect<0))
xinc=-xinc;
if((yinc>0 && yvect>0) || (yinc<0 && yvect<0))
yinc=-yinc;
collide=false;
x+=xinc;
y+=yinc;
//when the ball bumps against a boundary, it bounces off
//ball width is 6 so if the ball becomes less then 6 it is touching the frame
//if ball is greater than the entire width-the diameter of the rectangle, then the ball is just touching the frame of the rectangle and must switch to negative to go in opposit direction
if(x<6 || x>width-diameter){
xinc=-xinc;
x+=xinc;
//same thing as about just about the Y-axis instead of the x-axis
if(y<6 || y>height-diameter){
yinc=-yinc;
y+=yinc;
public void hit(CollideBall b){
if(!collide){
coll_x=b.getCenterX();
coll_y=b.getCenterY();
collide=true;
public void paint(Graphics gr){
g=gr;
g.setColor(color);
//the coordinates in fillOval have to be int, so we cast
//explicitly from double to int
g.fillOval((int)x,(int)y,diameter,diameter);
//Draws half white and half dark gray arc around the balls to give light and shadow effect
g.setColor(Color.white);
g.drawArc((int)x,(int)y,diameter,diameter,45,180);
g.setColor(Color.darkGray);
g.drawArc((int)x,(int)y,diameter,diameter,225,180);
public class BouncingBalls extends Applet implements Runnable {
Thread runner;
Image Buffer;
Graphics gBuffer;
CollideBall ball[];
//Obstacle o;
//how many balls?
static final int MAX=60;
boolean intro=true,drag,shiftW,shiftN,shiftE,shiftS;
boolean shiftNW,shiftSW,shiftNE,shiftSE;
int xtemp,ytemp,startx,starty;
int west, north, east, south;
public void init() {
Buffer=createImage(getSize().width,getSize().height);
gBuffer=Buffer.getGraphics();
ball=new CollideBall[MAX];
int w=getSize().width-5;
int h=getSize().height-5;
//our balls have different start coordinates, increment values
//(speed, direction) and colors
for (int i = 0;i<30;i++){
ball=new CollideBall(w,h,48+i,500+i,1.5,2.0,Color.white);
ball[i+30]=new CollideBall(w,h,890+i,200+i,1.5,2.0,Color.red);
public void start(){
if (runner == null) {
runner = new Thread (this);
runner.start();
/* public void stop(){
if (runner != null) {
runner.stop();
runner = null;
public void run(){
while(true) {
Thread.currentThread().setPriority(Thread.MAX_PRIORITY);
try {runner.sleep(15);}
catch (Exception e) { }
//move our balls around
for(int i=0;i<MAX;i++){
ball[i].move();
handleCollision();
repaint();
boolean collide(CollideBall b1, CollideBall b2){
double wx=b1.getCenterX()-b2.getCenterX();
double wy=b1.getCenterY()-b2.getCenterY();
//we calculate the distance between the centers two
//colliding balls (theorem of Pythagoras)
double distance=Math.sqrt(wx*wx+wy*wy);
if(distance<b1.diameter)
return true;
return false;
private void handleCollision(){
//we iterate through all the balls, checking for collision
for(int i=0;i<MAX;i++)
for(int j=0;j<MAX;j++){
if(i!=j){
if(collide(ball[i], ball[j])){
ball[i].hit(ball[j]);
ball[j].hit(ball[i]);
public void update(Graphics g){
paint(g);
public void paint(Graphics g) {
gBuffer.setColor(Color.lightGray);
gBuffer.fillRect(0,0,getSize().width,getSize().height);
gBuffer.draw3DRect(5,5,getSize().width-10,getSize().height-10,false);
//paint our balls
for(int i=0;i<MAX;i++)
ball[i].paint(gBuffer);
g.drawImage (Buffer,0,0, this);
Thanks again

this.user wrote:
JakeG27 post your code within the code tab it will be more clear.
You can do this by clicking on CODE when you do this will appear { code} { code} post your code inbetween those to tags.
ie
{ code} code... { code}
and it will look like this
code
This must be the first sensible post you've ever made. At least you're able to copy someone else's response and pretend you know something.

How to repaint a JPanel in bouncing balls game?

I want to repaint the canvas panel in this bouncing balls game, but i do something wrong i don't know what, and the JPanel doesn't repaint?
The first class defines a BALL as a THREAD
If anyone knows how to correct the code please to write....
package fuck;
//THE FIRST CLASS
class CollideBall extends Thread{
    int width, height;
    public static final int diameter=15;
    //coordinates and value of increment
    double x, y, xinc, yinc, coll_x, coll_y;
    boolean collide;
    Color color;
    Rectangle r;
    bold BouncingBalls balls; //A REFERENCE TO SECOND CLASS
    //the constructor
    public CollideBall(int w, int h, int x, int y, double xinc, double yinc, Color c, BouncingBalls balls) {
        width=w;
        height=h;
        this.x=x;
        this.y=y;
        this.xinc=xinc;
        this.yinc=yinc;
        this.balls=balls;
        color=c;
        r=new Rectangle(150,80,130,90);
    public double getCenterX() {return x+diameter/2;}
    public double getCenterY() {return y+diameter/2;}
    public void move() {
        if (collide) {
        x+=xinc;
        y+=yinc;
        //when the ball bumps against a boundary, it bounces off
        //bounce off the obstacle
    public void hit(CollideBall b) {
        if(!collide) {
            coll_x=b.getCenterX();
            coll_y=b.getCenterY();
            collide=true;
    public void paint(Graphics gr) {
        Graphics g = gr;
        g.setColor(color);
        //the coordinates in fillOval have to be int, so we cast
        //explicitly from double to int
        g.fillOval((int)x,(int)y,diameter,diameter);
        g.setColor(Color.white);
        g.drawArc((int)x,(int)y,diameter,diameter,45,180);
        g.setColor(Color.darkGray);
        g.drawArc((int)x,(int)y,diameter,diameter,225,180);
        g.dispose(); ////////
    ///// Here is the buggy code/////
    public void run() {
        while(true) {
            try {Thread.sleep(15);} catch (Exception e) { }
            synchronized(balls)
                move();
                balls.repairCollisions(this);
            paint(balls.gBuffer);
            balls.canvas.repaint();
//THE SECOND CLASS
public class BouncingBalls extends JFrame{
    public Graphics gBuffer;
    public BufferedImage buffer;
    private Obstacle o;
    private List<CollideBall> balls=new ArrayList();
    private static final int SPEED_MIN = 0;
    private static final int SPEED_MAX = 15;
    private static final int SPEED_INIT = 3;
    private static final int INIT_X = 30;
    private static final int INIT_Y = 30;
    private JSlider slider;
    private ChangeListener listener;
    private MouseListener mlistener;
    private int speedToSet = SPEED_INIT;
    public JPanel canvas;
    private JPanel p;
    public BouncingBalls() {
        super("fuck");
        setSize(800, 600);
        p = new JPanel();
        Container contentPane = getContentPane();
        final BouncingBalls xxxx=this;
        o=new Obstacle(150,80,130,90);
        buffer=new BufferedImage(getSize().width, getSize().height, BufferedImage.TYPE_INT_RGB);
        gBuffer=buffer.getGraphics();
        //JPanel canvas start
        final JPanel canvas = new JPanel() {
            final int w=getSize().width-5;
            final int h=getSize().height-5;
            @Override
            public void update(Graphics g)
               paintComponent(g);
            @Override
            public void paintComponent(Graphics g) {
                super.paintComponent(g);
                gBuffer.setColor(Color.ORANGE);
                gBuffer.fillRect(0,0,getSize().width,getSize().height);
                gBuffer.draw3DRect(5,5,getSize().width-10,getSize().height-10,false);
                //paint the obstacle rectangle
                o.paint(gBuffer);
                g.drawImage(buffer,0,0, null);
                //gBuffer.dispose();
        };//JPanel canvas end
        addWindowListener(new WindowAdapter() {
            @Override
            public void windowClosing(WindowEvent e) {
                System.exit(0);
        addButton(p, "Start", new ActionListener() {
            public void actionPerformed(ActionEvent evt) {
                CollideBall b = new CollideBall(canvas.getSize().width,canvas.getSize().height
                        ,INIT_X,INIT_Y,speedToSet,speedToSet,Color.BLUE,xxxx);
                balls.add(b);
                b.start();
        contentPane.add(canvas, "Center");
        contentPane.add(p, "South");
    public void addButton(Container c, String title, ActionListener a) {
        JButton b = new JButton(title);
        c.add(b);
        b.addActionListener(a);
    public boolean collide(CollideBall b1, CollideBall b2) {
        double wx=b1.getCenterX()-b2.getCenterX();
        double wy=b1.getCenterY()-b2.getCenterY();
        //we calculate the distance between the centers two
        //colliding balls (theorem of Pythagoras)
        double distance=Math.sqrt(wx*wx+wy*wy);
        if(distance<b1.diameter)
            return true;
        return false;
    synchronized void repairCollisions(CollideBall a) {
        for (CollideBall x:balls) if (x!=a && collide(x,a)) {
            x.hit(a);
            a.hit(x);
    public static void main(String[] args) {
        JFrame frame = new BouncingBalls();
        frame.setVisible(true);
} And when i press start button:
Exception in thread "Thread-2" java.lang.NullPointerException
at fuck.CollideBall.run(CollideBall.java:153)
Exception in thread "Thread-3" java.lang.NullPointerException
at fuck.CollideBall.run(CollideBall.java:153)
Exception in thread "Thread-4" java.lang.NullPointerException
at fuck.CollideBall.run(CollideBall.java:153)
and line 153 is: balls.canvas.repaint(); in Method run() in First class.
Please help.

public RepaintManager manager;
public BouncingBalls() {
        manager = new RepaintManager();
        manager.addDirtyRegion(canvas, 0, 0,canvas.getSize().width, canvas.getSize().height);
    public void run() {
        while(true) {
            try {Thread.sleep(15);} catch (Exception e) { }
            synchronized(balls)
                move();
                balls.repairCollisions(this);
            paint(balls.gBuffer);
            balls.manager.paintDirtyRegions(); //////// line 153
   but when push start:
Exception in thread "Thread-2" java.lang.IllegalMonitorStateException
at java.lang.Object.notifyAll(Native Method)
at fuck.CollideBall.run(CollideBall.java:153)
Exception in thread "Thread-3" java.lang.IllegalMonitorStateException
at java.lang.Object.notifyAll(Native Method)
at fuck.CollideBall.run(CollideBall.java:153)
i'm newbie with Concurrency and i cant handle this exceptons.
Is this the right way to do repaint?

Java Bouncing Balls Threads problem?

Hello,
I am working on a homework assignment to represent a java applet with some bouncing balls inside. So far so good. The balls bounce and behave as they are supposed. The only thing is that I want to make 2 buttons, Start and Stop (this is not part of the assignment, but my free will to provide some extra stuff :) ) . I am implementing Runnable for the animation and ActionListener for the buttons. I did research on threading, but somehow I am still not getting quite the result I want. The applet is not displaying my buttons (I guess I am not implementing them correctly) and I dont know whether I have synchronized the threads correctly as well. So, I am asking for some guidance how can I do this? Thanks in advance!
As a remark, I am new to Java, as I am just starting to learn it and this is my first assignment.
import java.awt.BorderLayout;
import java.awt.Color;
import java.awt.FlowLayout;
import java.awt.Graphics;
import java.awt.Image;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import javax.swing.JApplet;
import javax.swing.JButton;
import javax.swing.JPanel;
public class Balls extends JApplet implements Runnable, ActionListener
     Thread runner = null;
     Image img;
    Graphics gr;
    BallCollision ball[];
    Balls can;
    JButton stopButton;
    JButton startButton;
    JPanel controls;
    boolean stop,start;
    //field for 10 balls
    static final int MAX=10;
     public void init()
          setSize(800,600);
          img = createImage(size().width,size().height);
          gr = img.getGraphics();
          startButton = new JButton("Start");
          stopButton = new JButton("Stop");
          stopButton.addActionListener(this);
          startButton.addActionListener(this);
          controls = new JPanel();
          controls.setLayout(new FlowLayout());
          controls.add(startButton);
          controls.add(stopButton);
          //new Thread(this).start();
          ball = new BallCollision[MAX];
          int w=size().width;
          int h=size().height;
          //creation of balls, which have different coordinates,
          //speed, direction and colors
          ball[0] = new BallCollision(w,h,50,20,1.5,7.5,Color.orange);
        ball[1] = new BallCollision(w,h,60,210,2.0,-3.0,Color.red);
        ball[2] = new BallCollision(w,h,15,70,-2.0,-2.5,Color.pink);
        ball[3] = new BallCollision(w,h,150,30,-2.7,-1.0,Color.cyan);
        ball[4] = new BallCollision(w,h,210,30,2.2,-12.5,Color.magenta);
          ball[5] = new BallCollision(w,h,360,170,2.2,-1.5,Color.yellow);
          ball[6] = new BallCollision(w,h,210,180,-1.2,-2.5,Color.blue);
          ball[7] = new BallCollision(w,h,330,30,-2.2,-1.8,Color.green);
          ball[8] = new BallCollision(w,h,180,220,-2.2,-1.8,Color.white);
          ball[9] = new BallCollision(w,h,330,130,-2.2,9.0,Color.gray);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == startButton) start = true;
               can.start();
          if(e.getSource() == stopButton) start = false;
               can.stop();
     public void start()
          if (runner == null)
               runner = new Thread (this);
               runner.start();
     public void stop()
          if (runner != null)
              runner.stop();
                runner = null;
     public void run()
          while(true)
               try {Thread.sleep(15);}
                 catch (Exception e) { }
               //move our balls around
               for(int i=0;i<MAX;i++)
                    ball.move();
               handleCollision();
               repaint();
     boolean collide(BallCollision b1, BallCollision b2)
          double wx=b1.getCenterX()-b2.getCenterX();
          double wy=b1.getCenterY()-b2.getCenterY();
          //the distance between 2 colling balls' centres is
          //calculated by the theorem of Pythagoras
          double distance=Math.sqrt(wx*wx+wy*wy);
          if(distance<b1.diameter)
               return true;
               return false;
     private void handleCollision()
          //ecah ball is checked for possible collisions
          for(int i=0;i<MAX;i++)
               for(int j=0;j<MAX;j++)
                         if(i!=j)
                              if(collide(ball[i], ball[j]))
                                   ball[i].hit(ball[j]);
                                   ball[j].hit(ball[i]);
     public void update(Graphics g)
          paint(g);
     public void paint(Graphics g)
          gr.setColor(Color.black);
          gr.fillRect(0,0,size().width,size().height);
          //paint the balls
          for(int i=0;i<MAX;i++)
                    ball[i].paint(gr);
          g.drawImage (img,0,0, this);
class BallCollision
     int width, height;
     int diameter=30;
     //balls' coordinates and values to be incremented for directions
     double x, y, xIncremented, yIncremented, coll_x, coll_y;
     boolean collide;
     Color color;
     Graphics g;
     //constructor
     public BallCollision(int w, int h, int x, int y, double xInc, double yInc, Color c)
          width=w;
          height=h;
          this.x=x;
          this.y=y;
          this.xIncremented=xInc;
          this.yIncremented=yInc;
          color=c;
     public double getCenterX() {return x+diameter/2;}
     public double getCenterY() {return y+diameter/2;}
     public void move()
          if (collide)
               double xvect=coll_x-getCenterX();
               double yvect=coll_y-getCenterY();
               if((xIncremented>0 && xvect>0) || (xIncremented<0 && xvect<0))
                    xIncremented=-xIncremented;
               if((yIncremented>0 && yvect>0) || (yIncremented<0 && yvect<0))
                    yIncremented=-yIncremented;
               collide=false;
          x+=xIncremented;
     y+=yIncremented;
          //if the ball reaches a wall, it bounces to the opposite direction
     if(x<1 || x>width-diameter)
          xIncremented=-xIncremented;
               x+=xIncremented;
          if(y<1 || y>height-diameter)
               yIncremented=-yIncremented;
               y+=yIncremented;
     public void hit(BallCollision b)
          if(!collide)
               coll_x=b.getCenterX();
               coll_y=b.getCenterY();
               collide=true;
     public void paint(Graphics graphics)
          g=graphics;
          g.setColor(color);
          //the coordinates in fillOval have to be int, so we cast
          //explicitly from double to int
          g.fillOval((int)x,(int)y,diameter,diameter);

well i didnt arrive at this point without reading tutorials and researching.... sometimes other people can spot your mistakes a lot easier than you can, that's why I asked for help. 10x anyway for the interest!

Balls don't move in bouncing balls game.Please Help !?

I want to repaint the canvas panel in this bouncing balls game, but i do something wrong i don't know what, and the JPanel doesn't repaint?
The first class defines a BALL as a THREAD
If anyone knows how to correct the code please to write....
package ****;
//THE FIRST CLASS
class CollideBall extends Thread{
    int width, height;
    public static final int diameter=15;
    //coordinates and value of increment
    double x, y, xinc, yinc, coll_x, coll_y;
    boolean collide;
    Color color;
    Rectangle r;
    bold BouncingBalls balls; //A REFERENCE TO SECOND CLASS
    //the constructor
    public CollideBall(int w, int h, int x, int y, double xinc, double yinc, Color c, BouncingBalls balls) {
        width=w;
        height=h;
        this.x=x;
        this.y=y;
        this.xinc=xinc;
        this.yinc=yinc;
        this.balls=balls;
        color=c;
        r=new Rectangle(150,80,130,90);
    public double getCenterX() {return x+diameter/2;}
    public double getCenterY() {return y+diameter/2;}
    public void move() {
        if (collide) {
        x+=xinc;
        y+=yinc;
        //when the ball bumps against a boundary, it bounces off
        //bounce off the obstacle
    public void hit(CollideBall b) {
        if(!collide) {
            coll_x=b.getCenterX();
            coll_y=b.getCenterY();
            collide=true;
    public void paint(Graphics gr) {
        Graphics g = gr;
        g.setColor(color);
        //the coordinates in fillOval have to be int, so we cast
        //explicitly from double to int
        g.fillOval((int)x,(int)y,diameter,diameter);
        g.setColor(Color.white);
        g.drawArc((int)x,(int)y,diameter,diameter,45,180);
        g.setColor(Color.darkGray);
        g.drawArc((int)x,(int)y,diameter,diameter,225,180);
        g.dispose(); ////////
    ///// Here is the buggy code/////
    public void run() {
        while(true) {
            try {Thread.sleep(15);} catch (Exception e) { }
            synchronized(balls)
                move();
                balls.repairCollisions(this);
            paint(balls.gBuffer);
            balls.canvas.repaint();
//THE SECOND CLASS
public class BouncingBalls extends JFrame{
    public Graphics gBuffer;
    public BufferedImage buffer;
    private Obstacle o;
    private List<CollideBall> balls=new ArrayList();
    private static final int SPEED_MIN = 0;
    private static final int SPEED_MAX = 15;
    private static final int SPEED_INIT = 3;
    private static final int INIT_X = 30;
    private static final int INIT_Y = 30;
    private JSlider slider;
    private ChangeListener listener;
    private MouseListener mlistener;
    private int speedToSet = SPEED_INIT;
    public JPanel canvas;
    private JPanel p;
    public BouncingBalls() {
        super("****");
        setSize(800, 600);
        p = new JPanel();
        Container contentPane = getContentPane();
        final BouncingBalls xxxx=this;
        o=new Obstacle(150,80,130,90);
        buffer=new BufferedImage(getSize().width, getSize().height, BufferedImage.TYPE_INT_RGB);
        gBuffer=buffer.getGraphics();
        //JPanel canvas start
        canvas = new JPanel() {
            final int w=getSize().width-5;
            final int h=getSize().height-5;
            @Override
            public void update(Graphics g)
               paintComponent(g);
            @Override
            public void paintComponent(Graphics g) {
                super.paintComponent(g);
                gBuffer.setColor(Color.ORANGE);
                gBuffer.fillRect(0,0,getSize().width,getSize().height);
                gBuffer.draw3DRect(5,5,getSize().width-10,getSize().height-10,false);
                //paint the obstacle rectangle
                o.paint(gBuffer);
                g.drawImage(buffer,0,0, null);
                //gBuffer.dispose();
        };//JPanel canvas end
        addWindowListener(new WindowAdapter() {
            @Override
            public void windowClosing(WindowEvent e) {
                System.exit(0);
        addButton(p, "Start", new ActionListener() {
            public void actionPerformed(ActionEvent evt) {
                CollideBall b = new CollideBall(canvas.getSize().width,canvas.getSize().height
                        ,INIT_X,INIT_Y,speedToSet,speedToSet,Color.BLUE,xxxx);
                balls.add(b);
                b.start();
        contentPane.add(canvas, "Center");
        contentPane.add(p, "South");
    public void addButton(Container c, String title, ActionListener a) {
        JButton b = new JButton(title);
        c.add(b);
        b.addActionListener(a);
    public boolean collide(CollideBall b1, CollideBall b2) {
        double wx=b1.getCenterX()-b2.getCenterX();
        double wy=b1.getCenterY()-b2.getCenterY();
        //we calculate the distance between the centers two
        //colliding balls (theorem of Pythagoras)
        double distance=Math.sqrt(wx*wx+wy*wy);
        if(distance<b1.diameter)
            return true;
        return false;
    synchronized void repairCollisions(CollideBall a) {
        for (CollideBall x:balls) if (x!=a && collide(x,a)) {
            x.hit(a);
            a.hit(x);
    public static void main(String[] args) {
        JFrame frame = new BouncingBalls();
        frame.setVisible(true);
} This code draws only the first position of the ball:
http://img267.imageshack.us/my.php?image=51649094by6.jpg

I'm trying to draw everything first to a buffer:
buffer=new BufferedImage(getSize().width, getSize().height, BufferedImage.TYPE_INT_RGB);
gBuffer=buffer.getGraphics();
The buffer is for one JPanel and then i want to draw this buffer every time when balls change their possitions(collide or just move).
The logic is something like this:
startButton -> (ball.start() and add ball to List<balls>),
ball.start() -> ball.run() -> (move allballs, paint to buffer and show buffer)
In the first class:
BouncingBalls balls; //A REFERENCE TO SECOND CLASS
In the second class:
private List<CollideBall> balls=new ArrayList();
the tames are the same but this isn't an error.
Edited by: vigour on Feb 14, 2008 7:57 AM

Game and Ball Hit problem

Hello everyone, I am working on a game and was wondering if I could get some help. I have a ball that bounces around in a box, and place one small ball in the applet. I want to create an effect that when the ball that is moving comes into connect with the static ball, the moving ball bounces in the opposite direction. I used this:
if(x_pos - 100 < 2 & y_pos - 100 < 2 || 100-x_pos < 2 && 100 - y_pos < 2)
where x_pos and y_pos are for the moving ball, and 100 is the radius of the static ball. Should I use the Pythagoras theorem to do it?
Thank You In Advance for any help.

Use java.awt.Shape and its contains() method. It's a standard collision detection idiom.

Problem description: My macbook pro since this afteon has been slower, every application I open, it takes a long time to open, and shows the spinning beach ball for a while before it opens or performs some task, or responds to a click- EtreCheck

My computer
Problem description:
My macbook pro since this afternoon has been slower, every application I open, it takes a long time to open, and shows the spinning beach ball for a while before it opens or performs some task, or responds to a click…
EtreCheck version: 2.1.8 (121)
Report generated 31 de março de 2015 18:29:15 BRT
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
    MacBook Pro (13-inch, Early 2011) (Technical Specifications)
    MacBook Pro - model: MacBookPro8,1
    1 2.3 GHz Intel Core i5 CPU: 2-core
    16 GB RAM Upgradeable
        BANK 0/DIMM0
            8 GB DDR3 1333 MHz ok
        BANK 1/DIMM0
            8 GB DDR3 1333 MHz ok
    Bluetooth: Old - Handoff/Airdrop2 not supported
    Wireless: en1: 802.11 a/b/g/n
    Battery Health: Normal - Cycle count 250
Video Information: ℹ️
    Intel HD Graphics 3000 - VRAM: 512 MB
        Color LCD 1280 x 800
System Software: ℹ️
    OS X 10.10.2 (14C1514) - Time since boot: 0:25:47
Disk Information: ℹ️
    Hitachi HTS545032B9A302 disk0 : (320,07 GB)
        EFI (disk0s1) <not mounted> : 210 MB
        Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
        Macintosh HD (disk1) / : 318.84 GB (47.94 GB free) - 51 errors
            Core Storage: disk0s2 319.21 GB Online
    MATSHITADVD-R   UJ-898
USB Information: ℹ️
    Apple Inc. Apple Internal Keyboard / Trackpad
    Apple Inc. BRCM2070 Hub
        Apple Inc. Bluetooth USB Host Controller
    Apple Inc. FaceTime HD Camera (Built-in)
    Apple Computer, Inc. IR Receiver
Thunderbolt Information: ℹ️
    Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
    Mac App Store and identified developers
Launch Agents: ℹ️
    [not loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [loaded]    com.oracle.java.Java-Updater.plist [Click for support]
    [running]    com.trusteer.rapport.rapportd.plist [Click for support]
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist [Click for support]
    [loaded]    com.adobe.SwitchBoard.plist [Click for support]
    [loaded]    com.microsoft.office.licensing.helper.plist [Click for support]
    [loaded]    com.oracle.java.Helper-Tool.plist [Click for support]
    [loaded]    com.oracle.java.JavaUpdateHelper.plist [Click for support]
    [running]    com.trusteer.rooks.rooksd.plist [Click for support]
User Launch Agents: ℹ️
    [loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.google.keystone.agent.plist [Click for support]
    [running]    com.spotify.webhelper.plist [Click for support]
User Login Items: ℹ️
    iTunesHelper    UNKNOWN Hidden (missing value)
    AdobeResourceSynchronizer    Application Hidden (/Applications/Adobe Reader.app/Contents/Support/AdobeResourceSynchronizer.app)
    Stickies    Application (/Applications/Stickies.app)
Internet Plug-ins: ℹ️
    JavaAppletPlugin: Version: Java 8 Update 31 Check version
    FlashPlayer-10.6: Version: 17.0.0.134 - SDK 10.6 [Click for support]
    Default Browser: Version: 600 - SDK 10.10
    AdobePDFViewerNPAPI: Version: 10.1.13 [Click for support]
    AdobePDFViewer: Version: 10.1.13 [Click for support]
    Flash Player: Version: 17.0.0.134 - SDK 10.6 [Click for support]
    QuickTime Plugin: Version: 7.7.3
    SharePointBrowserPlugin: Version: 14.4.8 - SDK 10.6 [Click for support]
    Google Earth Web Plug-in: Version: 7.1 [Click for support]
    Silverlight: Version: 5.1.30514.0 - SDK 10.6 [Click for support]
    iPhotoPhotocast: Version: 7.0 - SDK 10.8
User internet Plug-ins: ℹ️
    npsf_cef: Version: sf 3.3.1.1 [Click for support]
    Google Earth Web Plug-in: Version: Unknown
Safari Extensions: ℹ️
    DivX HiQ
    DivX Plus Web Player HTML5 <video>
3rd Party Preference Panes: ℹ️
    Flash Player [Click for support]
    Java [Click for support]
    MacFUSE [Click for support]
    Perian [Click for support]
    Trusteer Endpoint Protection [Click for support]
Time Machine: ℹ️
    Skip System Files: NO
    Auto backup: YES
    Volumes being backed up:
        Macintosh HD: Disk size: 318.84 GB Disk used: 270.90 GB
    Destinations:
        Time Machine Backups [Local]
        Total size: 999.86 GB
        Total number of backups: 60
        Oldest backup: 2012-07-15 01:16:54 +0000
        Last backup: 2015-03-29 19:28:06 +0000
        Size of backup disk: Excellent
            Backup size 999.86 GB > (Disk size 318.84 GB X 3)
Top Processes by CPU: ℹ️
        97%    rapportd
         3%    WindowServer
         1%    mds
         0%    fseventsd
         0%    distnoted
Top Processes by Memory: ℹ️
    155 MB    Safari
    120 MB    Finder
    86 MB    rapportd
    86 MB    WindowServer
    69 MB    mds_stores
Virtual Memory Information: ℹ️
    12.56 GB    Free RAM
    2.53 GB    Active RAM
    428 MB    Inactive RAM
    1.66 GB    Wired RAM
    1.04 GB    Page-ins
    0 B    Page-outs
Diagnostics Information: ℹ️
    Mar 31, 2015, 06:00:15 PM    Self test - passed
    Mar 31, 2015, 01:13:05 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Microsoft Error Reporting_2015-03-31-131305_[redacted].crash
    Mar 31, 2015, 01:05:42 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Microsoft Error Reporting_2015-03-31-130542_[redacted].crash
    Mar 31, 2015, 12:24:33 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Microsoft Error Reporting_2015-03-31-122433_[redacted].crash
    Mar 30, 2015, 05:45:38 PM    /Library/Logs/DiagnosticReports/Skype_2015-03-30-174538_[redacted].cpu_resource .diag [Click for details]
    Mar 30, 2015, 01:52:07 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Last.fm Scrobbler_2015-03-30-135207_[redacted].crash
    Mar 29, 2015, 05:55:05 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/com.apple.WebKit.WebContent_20 15-03-29-175505_[redacted].crash
    Mar 29, 2015, 01:06:38 PM    /Library/Logs/DiagnosticReports/VLC_2015-03-29-130638_[redacted].hang
    Mar 29, 2015, 01:02:47 PM    /Library/Logs/DiagnosticReports/VLC_2015-03-29-130247_[redacted].hang

Open Activity Monitor and kill this process - rapportd.
Reinstalling OS X Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Reinstalling OS X Without Erasing the Drive
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility and press the Continue button. After Disk Utility loads select the Macintosh HD entry from the the left side list. Click on the First Aid tab, then click on the Repair Disk button. If Disk Utility reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit Disk Utility and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Alternatively, see:
Reinstall OS X Without Erasing the Drive
Choose the version you have installed now:
OS X Yosemite- Reinstall OS X
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
     Note: You will need an active Internet connection. I suggest using Ethernet
                 if possible because it is three times faster than wireless.

Why does Pages 09 hang for 1min30sec? The spinning ball, etc...

I am using Pages 09 version 4.3 (not the iWork package, just Pages 09)
Operating system 10.8.3 with 4 Gb memory on an iMac from around 2009 (Intel core 2 duo)
I had been using Quark Xpress for a couple decades and wanted to save a book I did in Pages so I can sell it in the Apple bookstore.
So I saved a Quark document as a pdf.
Then I used an on-line service to convert the pdf to a word document.
Then I opened the word doc in Pages and saved it as a Pages file.
I am in the process of doing a lot of reformatting, but I'm not surprised all the formatting didn't carry over, considering all the flie formats I went through.
The document is about 40 pages and has perhaps 40 pictures, but I do resize them in Photoshop so the Pages document file is only 4.9 Mb.
Pages isn't all that different from Quark, it just seems to hide things in different places.
The problem is that every so often when I click in the document, I get the spinning ball and Pages hangs for 1 minute and 30 seconds (doesn't it seem odd that it is always for the same length of time?). Then it comes out of its coma and I carry on.
Using the Activity Monitor I see Pages using 99.8% or 100% or even 100.5% of CPU. And The Pages line is in red type that reads "Pages (Not Responding).
While I wait for Pages to come to its senses, I can surf the Web, or use other programs, which seems peculiar because if the CPU is 100% occupied, I would think it could.
When I go to the dock and click on the Pages icon, it doesn't come to the front. I have to move any other windows so I can see my Pages document and click on it to bring it to the front.
I went into FontBook and checked all my fonts and deleted a bunch. When I reopened the document, it said it was missing a font, so I selected a substitute, the document opened and I re-saved it with a new name.
Sometimes it hangs when I click in text, but just now it was hanging every time I tried to click on a line behind the main text box.
Just now it hung when I started to go to the Edit menu. I waited and now it's back, as if nothing happened.
Any ideas?

After a very long night it seems my problems were solved by
1. making sure all the in-line pictures had the correct wrap around settings and
2. deleting some lines that had originally been underscores, but wound up being independent lines behind the main text box and
3. checking my fonts in FontBook and deleting the iffy ones (I dunno if this made any real difference, but I mention it anyway).
Every time I would select a line there would be a long pause. Initially 1 1/2 minutes, but shorter as I deleted the lines one by one.
There were also pauses when trying to select in-line pictures, and sometimes for no good reason that i could discern.
Anyway, now that the pictures' wrap around is re-set, and the lines are delected, there are bo more pauses!
Whew. I spent hours watching that ball spin. Still, it was better than re-creating the whole book.

New (8/14) Macbook Pro Retina - Premiere Pro CC 2014 spinning beach ball

Help! Seems my shiny new wiz-bang 4-core Macbook Pro with 16 GB of Ram and a 512 solid state drive works just fine with Adobe Premiere Pro CC 2014 until my project reaches a certain size, then it won't open the project and immediately gives me the deadly spinning beach ball. The only way to exit is to force quit whereupon I get the "Sorry, a serious error has occurred...". Aggravating beyond words.
Saw one forum comment where it was recommended to update to the 6.0 CUDA driver, but not even sure I have a CUDA driver. Plenty of space left on hard drive. In Premiere Pro preferences under the "Memory Tab" it doesn't seem to matter if it's set to "Optimize rendering for.... Memory or Performance." I've reinstalled the Premiere Pro App twice. Doesn't help.
Some specs:
Processor 2.5 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics Intel Iris Pro
NVIDIA GeForce GT 750M GPU PCie
Intel Iris Pro GPU Built-in
8 GB DDR# 1600 MHz (x2) = 16 GB RAM
350 GB of 499 GB left on drive
Of the 16 GB of RAM I have 11 available for Premiere Pro and the other 5 GB allocated for other apps.
Any suggestions would be greatly appreciated.

>NVIDIA GeForce GT 750M GPU PCie
>Intel Iris Pro GPU Built-in
Dual graphics adapters are a bane on civilization!!!
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
-Mac Utility for dual adapters http://forums.adobe.com/thread/1017891?tstart=0

New MBP - endless spinning ball :(

I have had this MBP for about six months. It is a 1.83 Ghz Intel Core Duo, OS10.4.8. I had the spinning ball problem from the beginning, so I upgraded my memory to 1.5 GB. That has helped only slightly.
Lately I have been using it more professionally, more often - Photoshop CS2, pretty big files back and forth, scanning, managing files, etc. I am encountering the spinning ball constantly: navigating between files, changing file sizes, opening files, and especially working with the Bridge (I think the File Browser was better, at least performance wise).
I am really, really disppointed with this machine. It is not fast, it does not perform well, and most frustratingly, as I've stated, I get the hanging spinning ball all the time. It feels like the six year old PC laptop my wife finally got rid of, not a state-of-the-art Mac laptop.
I called Apple a few months back and they said the warranty was only for hardware, and I had to troubleshoot software issues on the Apple site.
I also bought this machine in the States, and brough it here to the UK. (I don't know if that effects my warranty).
I can't work professionally with this product, I thought Apple was better than this - I also have a G5 desktop machine which works pretty well.
What should I do??
G5, dual 2Ghz Mac OS X (10.4.6)
G5, dual 2Ghz Mac OS X (10.4.6)
G5, dual 2Ghz Mac OS X (10.4.6)
G5, dual 2Ghz Mac OS X (10.4.6)
G5, dual 2Ghz Mac OS X (10.4.6)

Christopher, as others have mentioned, your problems are due to running legacy PPC apps via Rosetta emulation. And these are substantial programs with big RAM and CPU appetites.
Rosetta effectively doubles their RAM demands and cuts their performance by about 50% due to emulating PPC instructions on the fly.
The spinning balls are due to page outs in the Virtual Memory system, which uses the Hard Drive to make up for too little real RAM.
The more legacy apps you are running in Rosetta, the more virtual memory is used -- and this affects the responsiveness of all applications, even Intel native or Universal ones.
The solutions are: 1) run fewer legacy PPC apps; 2) get more RAM; 3) make sure you have adequate free space (at least 10% free) on your hard drive to allow VM to work efficiently.
If you fire up Utilities > Activity Monitor you can see which PPC legacy apps are running. Try to get that down to none. Activity Monitor will also tell you how many page-outs are occuring in Virtual Memory. My guess is: alot!

Beach balls and lock ups

ep... need some help with my issues that have been going on for a while.
turning off time machine reduced the temporary lock ups, but they still occur.
also have done a complete reinstall of leopard... issues still occur.
my setup... a mac pro.
programs randomly lock up, show a beach ball and force quits do not respond very quickly (sometimes it takes 1-2 minutes to get out of the stall).
adium, handbrake experience frequent stalls.
ical and fontbook won't open at all... just beachball and eventually quit.
firefox crashes about 2-4 times a day.
terminal is very crashy.
what can i do to solve these issues? i'd gladly reformat but the archive & install (without importing settings) barely improved the situation.
thanks for your time & effort to all those that assist...

holy crap i removed all the windows truetype and font fork (eh?) files from my system and fontbook now loads.
i had a feeling it was font related, but things are looking up...
will post more findings...

Beash ball woes revisited

Similar Messages

Maybe you are looking for