This discussion is archived
1399 Views 11 Replies Latest reply: Dec 2, 2006 7:02 AM by Joe Burgess
Currently Being ModeratedApr 17, 2006 2:18 PM (in response to SStreet)Can you sample it to see what Front Row is doing?
To do this, double click on the Front Row application listed in Activity Monitor and click the Sample button.
Or, in Terminal:
% sample Front\ Row 5
by looking at that we might be able to determine what's going on. I'd bet its stuck in a call to some font code...G5, G4s, Mac Book Pro, DC mini, Mac OS X (10.4.6)
Currently Being ModeratedApr 17, 2006 9:29 PM (in response to SStreet)Just my luck, after posting eariler today, I get information to collect a sample, and if figures; after two days of trying to figure out why FR was running away -- now I can't reproduce the problem. Darn Murphy's Law!iMac 20" Intel 2.0GHz, Mac OS X (10.4.6)
Currently Being ModeratedApr 17, 2006 9:31 PM (in response to SStreet)Looks to have been a fluke... guess I'll keep my eye on it in the future.
Currently Being ModeratedApr 27, 2006 11:55 AM (in response to SStreet)I have had the exact same problem all along and it happens almost every time I use the remote. I clued into it because after using Front Row and returning to the Finder (or anything else) the machine is painfully slow to do anything.
I'll try the smaple idea posted here and see what happens, but I just wanted to let you know that your problem is not just you!
bbMacBook Pro 1.83/2GB RAM, Mac OS X (10.4.6)
Currently Being ModeratedMay 8, 2006 1:43 PM (in response to SStreet)Mine does the exact same thing, and now (of course) I can't recreate it. Next time (there will be one, this happens quite often) I'll do the inspect thing.
I find it usually happens more often if I cancel it from finding shared music or movie trailers.MacBook Pro, Mac OS X (10.4.6)
Currently Being ModeratedMay 9, 2006 9:27 AM (in response to SStreet)I have this problem consistently. Front Row running in the background taking up ~%96 of the processor capacity. I can see this through the system monitor widget. However, Front Row does not show up under the Apple --> Force Quit menu. It's like a hidden process? (I didn't know mac's hid their processes). Sometimes I can get back into Front Row and use the "apple-Q" force quit command, and that will bring me back to desktop and everything works fine and the processor capacity is released. I can then even get back into Front Row and it will work just fine until the next unexpected front-row crash.
Unfortunately, sometimes when I am at the desktop and, having noticed that Front Row is crashing in the background, *I cannot get back into Front Row* either by apple remote or "Apple-Esc". And as I said, Front Row does not show up under Apple->ForceQuit. So I am forced to restart the computer.
Note: Front Row crashes at LEAST everyday, about every 3rd time I use it. I haven't confirmed this, but I'm pretty sure it doesn't matter what type of media has been played under Front Row to cause a crash. I'm kind'a hoping it's a bug that's secretly fixed in the next OS updateiMac G5 1.9Ghz 1.5Gb ram w/ buit-in iSight, Mac OS X (10.4.4)
Currently Being ModeratedMay 9, 2006 9:37 AM (in response to Jmoy)You can kill Front Row with the Activity Monitor utility. This will show foreground and background processes (which Front Row is the latter).
When you say front-row crash, do you mean where Front Row goes away unexpectedly or is hammering the CPU?
Can you post the last crash log? (Open Console.app in Utilities and disclose the ~/Library/Logs arrow in the Logs listing, then disclose the CrashReporter arrow and select the Front Row.crash.log item. If there are a bunch of crashes in the log, just select the last one.G5, G4s, Mac Book Pro, DC mini, Mac OS X (10.4.6)
Currently Being ModeratedMay 13, 2006 11:23 PM (in response to Kevin Arnold)Hi Kevin Arnold, thanks for the tip on force-quitting through Activity Monitor. It worked and freed the CPU resources -- Plus I can get back into Front Row and it seems to work (until the next crash...) so maybe now I won't have to restart everytime this happens!
When I say Front Row crashes, I mean that it hammers the CPU in the background. It never actually crashes with an error message, it just fails to quit sometimes (often) when going back to the desktop. Also on occassion, FrontRow HAS started 'hammering the CPU' while still running in the foreground and I get stuck inside FrontRow unable to return to the desktop; but in this case, apple-Q WILL work within Front Row to kill the app and return everything to normal.
My FrontRow just crashed again a minute ago, so I ran the % sample Front\ Row 5 terminal command you posted earlier for someone else, and the result said 'bash: no such process'. **yes, I ran the command before force-quitting through application monitor**
Here are the last few lines from FrontRow.Crash.Log:
0x97355000 - 0x97362fff com.apple.agl 2.5.6 (AGL-2.5.6) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x97463000 - 0x9747dfff com.apple.AppleVAFramework 2.4.24 /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x976ab000 - 0x976c1fff com.apple.AppleShareClient 1.5.1 /System/Library/Frameworks/AppleShareClient.framework/Versions/A/AppleShareClie nt
0x976cb000 - 0x97709fff com.apple.AppleShareClientCore 1.5.1 /System/Library/Frameworks/AppleShareClientCore.framework/Versions/A/AppleShare ClientCore
0x9781b000 - 0x97a01fff com.apple.dvdplayback 4.6.6 (4660) /System/Library/Frameworks/DVDPlayback.framework/Versions/A/DVDPlayback
0x985a2000 - 0x9864cfff com.apple.applescript 1.10.6 /System/Library/PrivateFrameworks/AppleScript.framework/Versions/A/AppleScript
0x987e1000 - 0x987e3fff com.apple.BezelServicesFW 1.3.7 /System/Library/PrivateFrameworks/BezelServices.framework/Versions/A/BezelServi ces
0x9908e000 - 0x99190fff com.apple.audio.units.Components 1.4.1 /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
I hope you can make sense of all that crash log mumbo jumbo.iMac G5 1.9Ghz 1.5Gb ram w/ buit-in iSight, Mac OS X (10.4.6)
Currently Being ModeratedMay 14, 2006 2:53 PM (in response to Jmoy)Actually I need the entire last crash log, or at the very least the thread backtrace that actually crashed. Unfortunately the portion that you pasted just shows the loaded shared libraries.G5, G4s, Mac Book Pro, DC mini, Mac OS X (10.4.6)
Currently Being ModeratedMay 24, 2006 6:51 PM (in response to Kevin Arnold)I think Apple has fixed the bug. Last week there was an update to Front Row issued under the apple software updates, and ever since downloading this, Front Row has not crashed. I'll cross my fingers, but am happy that Front Row has at least stabilized and hasn't 'runaway' for a week now!iMac G5, Mac OS X (10.4.4)
Currently Being ModeratedDec 2, 2006 7:02 AM (in response to Jmoy)I would just like to say that my computer has been doing this since I got it in Dec of 2005. It is a iMac G5. After about 3 minutes of watching different videos, especially dl.tv, it will go very slow. I will then menu out of front row and my menumeters says I have 100% cpu usage. It is all being used by front row. Here(http://rootsmart.com/Sample%20of%20Front%20Row.txt) is a sample of front row while it is at its 100%. That is the text file I got, and I just uploaded it to my site.
Thanks!20" iMac G5 w/ iSight, Mac OS X (10.4.8)