Force Quit

Joined
Oct 1, 2004
Messages
55
Reaction score
0
Points
6
Location
Santa Fe, NM
Your Mac's Specs
12" G4 Powerbook & 80g iPod classic
What causes an application to spaz out so that you have to force quit the app? This has happened with my Word and Proteus apps. I understand that this happens on windows machines too, just curious if there was an answer for macs that is a little more sufficient than the windows standard "sometimes it just happens."
 
M

m1k

Guest
Well, Word is made by Microsoft, so the answer for Word is 'Sometimes it just happens'....

I don't know about Proteus though, what kind of program is it?
 
Joined
Mar 30, 2004
Messages
4,744
Reaction score
381
Points
83
Location
USA
Your Mac's Specs
12" Apple PowerBook G4 (1.5GHz)
Well, the reason it "just happens" (on any platform) is because of an error in the code. The programmer(s) who wrote it screwed up. Maybe the software tried to access a bit of memory that was off limits, or maybe it kept looping when it should have stopped, or maybe it should have taken one branch but instead it took another.

All software has bugs. Some programs have more than others, and some are more serious than others. Some companies (Ahem) tend to produce software of lower quality than others. OS X can't fix the bugs that programmers create, but it tends to limit their impact fairly well; ie, one bad program doesn't bring down the whole computer.
 
S

SamR

Guest
I seem to get the color-pinwheel of death a lot more frequently than w/ windows
 
Joined
Jun 11, 2003
Messages
4,915
Reaction score
68
Points
48
Location
Mount Vernon, WA
Your Mac's Specs
MacBook Pro 2.6 GHz Core 2 Duo 4GB RAM OS 10.5.2
I use Word quite a bit and Proteus all the time.. I don't either one of those problems. Maybe a bad install? maybe bad preferences.. bad permissions on those preferences? It could be a lot of things.
 
T

Toanjii

Guest
Hi,

Sorry but I don't have an answer but only want to add to your query.

I was using Azureus when it died on my for 4 minutes to quit. So I forced quit and it came up with a debug log file (no idea what that is) but I deleted it.

Can I ask does force quitting cause corruption/damage of the app or OS X in anyway?

Thanks heaps.
 

rman


Retired Staff
Joined
Dec 24, 2002
Messages
12,637
Reaction score
168
Points
63
Location
Los Angeles, California
Your Mac's Specs
14in MacBook Pro M1 Max 32GB 2TB
Toanjii said:
Can I ask does force quitting cause corruption/damage of the app or OS X in anyway?

Thanks heaps.

No. Terminating the application will not cause problems in most cases. There are times when the program/application screwed everything so bad that force quiting does nothing and only a reset/reboot wil solve the problem.
 
T

Toanjii

Guest
rman said:
No. Terminating the application will cause problem in most cases. There are times when the program/application screwed everything so bad that force quiting does nothing and only a reset/reboot wil solve the problem.

Hi rman,

Sorry but I'm a bit confused about what you mean by "no" then the following sentences. So does it cause problems/damage to OS X or the app?

Thanks heaps.

Toan.
 

rman


Retired Staff
Joined
Dec 24, 2002
Messages
12,637
Reaction score
168
Points
63
Location
Los Angeles, California
Your Mac's Specs
14in MacBook Pro M1 Max 32GB 2TB
Sorry Toanjii, I forgot the word not in the first sentence.

As in "Terminating the application will not cause problems in most cases."
 

Shop Amazon


Shop for your Apple, Mac, iPhone and other computer products on Amazon.
We are a participant in the Amazon Services LLC Associates Program, an affiliate program designed to provide a means for us to earn fees by linking to Amazon and affiliated sites.
Top