526347 - crash on attempting to 'Save as' with Mac OS X Server cache redirection enabled for clients

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: General, defect)

Description

[Brian Bowell (ICT Support)]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_7; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9
Build Identifier: Camino 1.6.10

Any attempt to 'Save as' a page results in Camino crashing. This happens regardless of the page being viewed.

Reproducible: Always

Steps to Reproduce:
1. Launch Camino
2. Load a URL
3. Select 'File > Save as'
4. Camino crashes with an 'Unexpected Error' message.
Actual Results:  
Camino Crashed

Expected Results:  
A 'Save as' dialogue box. Allowing the user to save the page

Machines are iMac & MacBook workstations with 10.5.7 Leopard, managed by an Intel XServe running Leopard Server.

Comment 1

[Brian Bowell (ICT Support)]

Attachment: Apple Crash Reporter document

Comment 2

[Chris Lawson (gone)]

Does this happen with a fresh profile, or with the latest Camino 2.0rc build? How about in any other apps?

It sounds like you've got something that's modifying the OS-native save dialog installed, and we've seen similar crashes before. What happens if you remove this thing:

 0x1209000 -  0x120affc +com.prometheanworld.extenderbridge ??? (1.0) /Library/InputManagers/Promethean/Extender.bundle/Contents/MacOS/Extender

restart, and try again?

Comment 3

[Stuart Morgan]

Looks like one of the core objects is NULL. It would be very helpful if you could install the release candidate of Camino 2.0 from http://tinyurl.com/Cm20rc1 and reproduce this, then submit the crash through Camino's crash reporter. Then you can go to "about:crashes" in the location bar and get the ID of the crash, and post it here.

That would give us a line number, so we could see exactly what is NULL.

Comment 4

[Brian Bowell (ICT Support)]

Yes. It happens with a fresh profile.

It only happens with Camino.

There is no such file with the path: '/Library/InputManagers/Promethean/Extender.bundle/Contents/MacOS/Extender' on the workstations or users' Home Directory.

Where will I find 'the release candidate of Camino 2.0' at 
http://tinyurl.com/Cm20rc1 please?

Brian Bowell
ICT Support Berkley School

Comment 5

[Chris Lawson (gone)]

(In reply to comment #4)
> Yes. It happens with a fresh profile.
> 
> It only happens with Camino.
> 
> There is no such file with the path:
> '/Library/InputManagers/Promethean/Extender.bundle/Contents/MacOS/Extender' on
> the workstations or users' Home Directory.

That's because that isn't a home directory path. It's the path to the main Library folder on the boot volume.

> Where will I find 'the release candidate of Camino 2.0' at 
> http://tinyurl.com/Cm20rc1 please?

It's the only file in that directory.

Comment 6

[Brian Bowell (ICT Support)]

I have solved this problem myself, albeit accidently. Our users Home Directories use cache redirection to manage the size of caches in student Home Directories. Restoring default caching cured the problem I was working, and also the 'Save as' issue with Camino.

Thanks to everyone for their help.
Brian Bowell.

Comment 7

[Chris Lawson (gone)]

Can you explain a little bit more about the specific setup you guys are using, and whether Camino 2.0rc is also susceptible to the crash? If there's a genuine crash bug here, we need to fix it regardless of whether there's a workaround :)

cl

Comment 8

[Brian Bowell (ICT Support)]

We have an Xserve running Leopard Server. iMac, MacBook and MacBook Pro workstations running Leopard. There has been an ongoing problem here with FireFox. Some users could use it and for others it would never launch. We needed FireFox as well as Apple's Safari, because FireFox does some things that Safari doesn't. The engineers who do our server builds suggested I trial Camino as an alternative.

I posted a query on the Macintosh Manager group and several postings pointed to cache redirection as the cause of the issue. After a further look at users' Home Directories it became clear that users with cache redirection could not use FireFox, those with a /Library/Caches folder could. Removing redirection and creating a Caches folder cured the problem with FireFox. 

Once I'd done that I tried Camino again,with users having no cache redirection. The 'Save as' function now works.

I'll certainly try a download of Camino 2.0rc here as soon as I can and report back.

Brian Bowell.

Comment 9

[Brian Bowell (ICT Support)]

I have installed Camino 2.0rc. When a user with cache redirection attempts a 'Save as', Camino quits as before. Remove redirection and Camino behaves normally.

When a user without redirection runs Camino 2.0rc it performs normally as well. Removing redirection solves the problem.

Brian Bowell.

Comment 10

[Stuart Morgan]

Could you post the submitted crash ID? (See comment 3)

Comment 11

[Chris Lawson (gone)]

Brian, we need an answer to comment 3/comment 10.

Comment 12

[Chris Lawson (gone)]

Brian, if you can't provide us an answer to comment 3/comment 10, we're going to have to close this bug.

Comment 13

[Chris Lawson (gone)]

INCOMPLETE because we never got any more answers. If you can provide the information we requested, feel free to re-open the bug. (And we'll need you to reproduce the crash again at this point, because I'm sure any crash ID from November 2009 has expired by now.)