341027 - Inexplicable crash bug in 1.0.1 and 1.0.2RC on 10.2.8

Status: VERIFIED INVALID

(Camino Graveyard :: General, defect)

Description

[Cameron Kaiser [:spectre]]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.3) Gecko/20060427 Camino/1.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.3) Gecko/20060427 Camino/1.0.1

(no Talkback available)

Hard crash on 10.2.8, consistent, with this URL (given above): http://ukcc.uky.edu/~ukccinfo.391/primeug.html

Does not seem to exist on 10.3.9 or 10.4.6, and does not occur when I download the file (using Lynx) and view it locally in Camino.

Reproducible: Always

Steps to Reproduce:
1. Surf to URL.
2. Pick browser off of ground.

Actual Results:  
Page starts to load, and then bombs out. Crash log reported by Console.

Expected Results:  
Should work!

Comment 1

[Cameron Kaiser [:spectre]]

Attachment: Camino crash log

(output from Crash log)

Comment 2

[Chris Lawson (gone)]

This is just a shot in the dark, but if you grab all the images off that page, are any of them corrupted when viewed in GraphicConverter?

It looks like the TIFF caching routines are crapping out on Jaguar. FWIW, this is  WONTFIX, as we've stopped supporting 10.2, unless someone can come up with a fix before the end of the 1.0.x cycle.

cl

Comment 3

[Samuel Sidler (old account; do not CC)]

This bug is *not* a WONTFIX if it's a regression from Camino 1.0.1 to 1.0.2RC. Camino 1.0.x still supports Mac OS X 10.2.8 and if we regressed something, it needs to be fixed.

Comment 4

[Chris Lawson (gone)]

BTW, does this happen in 1.0 (not 1.0.1)?

cl

Comment 5

[Torben]

> BTW, does this happen in 1.0 (not 1.0.1)?

Yes.

However, the problem is not the page but the favicon, after changing browser.chrome.favicon to false I get no crash on 10.2.8

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

So http://ukcc.uky.edu/favicon.ico is corrupt (and served as text/plain); on 10.3.9, Preview warns you this is the case (Iconographer hangs, and GraphicConverter displays the corrupt favicon).  We display a blank "image" in the location bar but Safari and Firefox both keep their default globe (we should probably do that, but that's another bug).

This bug is INVALID as an OS bug, as far as I can tell from the reports (does Safari on 10.2 support display of favicons, and if so, does it also crash?).

Comment 7

[Torben]

> does Safari on 10.2 support display of favicons, and if so, does it also
> crash?

Yes, and yes (with basically the same crash log as Camino).

> So http://ukcc.uky.edu/favicon.ico is corrupt (and served as text/plain)

Are there any (easy) way we could detect this and not load the favicon?

Comment 8

[Cameron Kaiser [:spectre]]

Could there be a hack to disallow loading favicons with text/plain, at least for 10.2.8? I know this would cause a *lot* of favicons to not load, but that's better than the alternative (especially since it's the wrong MIME type anyway).

Comment 9

[Chris Lawson (gone)]

Cameron, can you dig around in Bugzilla and see if comment 8 is already filed as a separate bug (probably against Core)? If not, it's arguably something that should be done.

cl

Comment 10

[Cameron Kaiser [:spectre]]

(In reply to comment #9)
> Cameron, can you dig around in Bugzilla and see if comment 8 is already filed
> as a separate bug (probably against Core)? If not, it's arguably something that
> should be done.
> 
> cl
> 

How about Core bug #110077? At the bottom they bring up the text/plain issue, think that would be a good one to tag onto? Or introduce it as a new issue?

Comment 11

[Chris Lawson (gone)]

(In reply to comment #10)
> How about Core bug #110077? At the bottom they bring up the text/plain issue,
> think that would be a good one to tag onto? Or introduce it as a new issue?

Not that one, since that bug is about displaying no icon at all (not even the default bookmark icon) in cases where the favicon is invalid. I can't seem to find an appropriate bug for it.

Regardless, the problem you're having would exist even if the server were sending the proper MIME type, and since future Camino versions (1.1 and up) will be dropping support for 10.2.x, this is such a minor issue that it's probably not worth worrying about.

I'll look into filing a bug on rejecting text/plain favicons, though.

cl