Ticket #172 (closed Defect: invalid)

Opened 7 years ago

Last modified 6 years ago

sapphire b6 & b6.1: Freeze followed by Front Row crash when run as Standard User

Reported by: srcshelton@… Owned by:
Priority: normal Milestone:
Component: Other Version: 1.0b6.1
Keywords: Cc:

Description

I have a Mac Mini (2,1) with two users: my Admin user, and then a 'Media Centre' Standard User for all to use to watch movies.

Running sapphire 1.0b6 and 1.0b6.1 as my Admin user is completely fine - no problems.

However, when Front Row starts as the Standard User, I do see the Sapphire "S" icon. However, if I select this then everything freezes up for several minutes, at which point I'm dropped back to the desktop.

The crash-logs all say:

Process:         Front Row [7632]
Path:            /System/Library/CoreServices/Front Row.app/Contents/MacOS/Front Row
Identifier:      com.apple.frontrow
Version:         2.1.3 (2.1.3)
Build Info:      FrontRow-2330000~5
Code Type:       X86 (Native)
Parent Process:  launchd [203]

Date/Time:       2008-05-15 22:38:15.609 +0100
OS Version:      Mac OS X 10.5.2 (9C7010)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
Crashed Thread:  0

Thread 0 Crashed:
0   com.apple.CoreFoundation      	0x9198e85d _CFArrayReplaceValues + 2397
1   com.apple.CoreFoundation      	0x91a68f3b -[__NSPlaceholderArray initWithObjects:count:] + 363
2   com.apple.CoreFoundation      	0x91a6bd34 +[NSArray array] + 68
3   com.apple.Foundation          	0x91378e78 _NSDirectoryContentsFromCarbonError + 56
4   com.apple.Foundation          	0x91378ba0 -[NSFileManager directoryContentsAtPath:matchingExtension:options:keepExtension:error:] + 320
5   com.apple.Foundation          	0x91378a57 -[NSFileManager directoryContentsAtPath:matchingExtension:options:keepExtension:] + 71
6   com.apple.Foundation          	0x91378a05 -[NSFileManager directoryContentsAtPath:] + 69
7   ...frontrow.appliance.Sapphire	0x129ca491 -[SapphireDirectoryMetaData reloadDirectoryContents] + 145
8   ...frontrow.appliance.Sapphire	0x129cc5b4 -[SapphireDirectoryMetaData invokeRecursivelyOnFiles:withPredicate:] + 36
9   ...frontrow.appliance.Sapphire	0x129cc606 -[SapphireDirectoryMetaData invokeRecursivelyOnFiles:withPredicate:] + 118
<...>
511 ...frontrow.appliance.Sapphire	0x129cc606 -[SapphireDirectoryMetaData invokeRecursivelyOnFiles:withPredicate:] + 118

Is there any other useful data I could provide to help to diagnose this problem?

(The figure 511 seems suspicious - is 512 a hard system limit? Why does this crash seemingly affect only Standard Users - if it were a permissions issue, I'm assuming that that would have been detected without crashing? I guess that the delay between selecting the Sapphire icon and the crash is the time it takes for the attempts to recursively scan the filesystem...)

One thing worth mentioning: In 'Media Centre's home directory is:

macmini:~ Media$ ls -l ~/Movies/
total 56
lrwxr-xr-x  1 Media  Media  27 Nov  5  2007 DVDs -> /Volumes/Storage/Media/DVDs
lrwxr-xr-x  1 root   Media   8 Feb  4 23:04 Drives -> /Volumes
lrwxr-xr-x  1 Media  Media  28 Dec  5 17:38 Films -> /Volumes/Storage/Media/Films
lrwxr-xr-x  1 Media  Media  25 Dec  5 17:38 Incoming -> /Volumes/Storage/Incoming
lrwxr-xr-x  1 Media  Media  35 Dec 12 00:22 Music Videos -> /Volumes/Storage/Media/Music Videos
lrwxr-xr-x  1 Media  Media  33 Nov  5  2007 Television -> /Volumes/Storage/Media/Television
lrwxr-xr-x  1 Media  Media  29 Dec  5 17:38 Videos -> /Volumes/Storage/Media/Videos

... where Storage is an auto-mounted NFS share. Could the 'Drives' symlink be creating a loop?

Change History

comment:1 Changed 7 years ago by gbooker

Looks like a stack overflow... Admin users have different limits on the stack size, which could be the difference. Look at the "launchctl limit" command to see the current limits, and I think it can change them too, but it's been a while since I fiddled with these.

Definitely see if there is a symlink loop. In theory, Sapphire should detect this, but that code has never been fully tested, so it may not work.

comment:2 Changed 6 years ago by gbooker

  • Status changed from new to closed
  • Resolution set to invalid

No reply; closing

Note: See TracTickets for help on using tickets.