 |
 |
Firefox crash in classic
|
|
|
|
|
Mac Elite
Join Date: Sep 2001
Location: Chico, CA and Carlsbad, CA.
Status:
Offline
|
|
Anyone seen this? Click the picture for a full sized screenshot.
This was in Firefox .9.3 on Mac OS 10.3.4. I got a Classic-style bomb error saying Firefox had crashed but it had clearly not. Clicking "restart" did nothing. I killed Classic and the error went away... cool.
Weird, anyone seen this? 
(Last edited by [APi]TheMan; Sep 10, 2004 at 11:51 AM.
)
|
"In Nomine Patris, Et Fili, Et Spiritus Sancti"
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Oct 1999
Location: San Jose, Ca
Status:
Offline
|
|
FireFox is not a classic application, it has never been, and will never be. If it mistakenly has gotten the "Start in Classic" flag, then you need to uncheck this in the finder.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2001
Location: Cambridge UK
Status:
Offline
|
|
Originally posted by larkost:
FireFox is not a classic application, it has never been, and will never be. If it mistakenly has gotten the "Start in Classic" flag, then you need to uncheck this in the finder.
That's not what he means - i.e. Firefox affected Classic somehow.
Very odd...
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Nov 1999
Status:
Offline
|
|
Originally posted by Krypton:
That's not what he means - i.e. Firefox affected Classic somehow.
Very odd...
More likely, Classic tried to access OSX's process list, and picked the wrong one by mistake.
What Classic apps were you running at the time? Can you reproduce this reliably?
|
|
You are in Soviet Russia. It is dark. Grue is likely to be eaten by YOU!
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Sep 2001
Location: Chico, CA and Carlsbad, CA.
Status:
Offline
|
|
Originally posted by Krypton:
That's not what he means - i.e. Firefox affected Classic somehow.
Very odd..
Correct, I guess I was unclear that I was aware of the fact that Firefox is not a Classic application. 
Originally posted by Millennium:
More likely, Classic tried to access OSX's process list, and picked the wrong one by mistake.
What Classic apps were you running at the time? Can you reproduce this reliably?
Strange indeed. I was only running Microsoft Outlook 2001 in Classic at the moment (I was troubleshooting Exchange server problems that I was having in Entourage 2004). I have been at work all day and have not had a chance to try to reproduce the error.
The error was totally unthreatening minus the fact that it would not dismiss... Killing Classic was merely to clear the error
|
"In Nomine Patris, Et Fili, Et Spiritus Sancti"
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
