Bug 11958 – Sporadic console message: TIFFReadDirectory: tiff data provider: Seek error accessing TIFF directory.

• Component: New Bugs
• Status: RESOLVED INVALID

[David Kilzer (:ddkilzer)]

Every now and then I see the following message spewed to the console (usually in groups of 20+):

TIFFReadDirectory: tiff data provider: Seek error accessing TIFF directory.

I don't have any idea what's causing it (e.g., which web page or which behavior of mine), but I thought I'd report it in case anyone else has an idea.

I have to wonder if removing the old TIFF cursors in place of PNG cursors has something to do with this.  I also wonder if it's something within Safari (and not WebKit) that is causing the message to be logged.

Bug 8457 mentions "TIFFReadDirectory", but that's the only remotely related bug I could find.

[David Kilzer (:ddkilzer)]

(In reply to comment #0)
> I have to wonder if removing the old TIFF cursors in place of PNG cursors has
> something to do with this.

Bug 11291 and Bug 11940 are related to this change.

[Alexey Proskuryakov]

Do you have any TIFF files in your cache? It can be browsed using /Developer/Examples/WebKit/DiskCacheInspector.

[David Kilzer (:ddkilzer)]

(In reply to comment #2)
> Do you have any TIFF files in your cache? It can be browsed using
> /Developer/Examples/WebKit/DiskCacheInspector.

When I build it and run it from within Xcode, I can't get the search box to get focus (typing always goes to another window.  If I try to run the application outside Xcode, I get an error dialog saying the app is corrupt.  Am I doing something stupid?

[Alexey Proskuryakov]

Heh, there is a bug in the current release - an incorrect Info.plist. Just fix CFBundleExecutable from DiskCacheInpector to DiskCacheInspector. Might be worth a Radar, too.

[David Kilzer (:ddkilzer)]

(In reply to comment #4)
> Heh, there is a bug in the current release - an incorrect Info.plist. Just fix
> CFBundleExecutable from DiskCacheInpector to DiskCacheInspector. Might be worth
> a Radar, too.

Thanks!  Filed <rdar://problem/4900777> for this typo.

[David Kilzer (:ddkilzer)]

(In reply to comment #2)
> Do you have any TIFF files in your cache? It can be browsed using
> /Developer/Examples/WebKit/DiskCacheInspector.

No, I don't have an TIFF files in my cache (at least after searching for 'tif' and then checking the MIME type of each of the six hits).

Apparently this happens when Safari tries to load a TIFF image that is corrupt or otherwise unloadable.  This web page seems to generate them:

http://www.oreillynet.com/mac/blog/2006/04/sucking_out_the_itunes_marrow.html

I fond it by doing a Google search for "TIFFReadDirectory: tiff data provider: Seek error accessing TIFF directory."

[David Kilzer (:ddkilzer)]

This TIFF image always causes the error message to be displayed:

http://www.oreillynet.com/mac/blog/images/0604iTunesPicscaled.tiff

[David Kilzer (:ddkilzer)]

Created attachment 12022 [details]
0604iTunesPicscaled.tiff (causes warnings)

[David Kilzer (:ddkilzer)]

(In reply to comment #8)
> Created an attachment (id=12022) [edit]
> 0604iTunesPicscaled.tiff (causes warnings)

Now that I've found the cause, what should be the fix?  Should Safari not spew these messages to the console?  Or only send one copy of this message to the console?

[Alexey Proskuryakov]

FWIW, I don't see WebKit using libtiff directly, so this looks like Radar material, too.

[David Kilzer (:ddkilzer)]

(In reply to comment #10)
> FWIW, I don't see WebKit using libtiff directly, so this looks like Radar
> material, too.

Filed <rdar://problem/4900968> Some TIFF files cause message to be logged repeatedly to console in Safari.  Closing as RESOLVED/INVALID since this can't be fixed in WebKit.

[David Kilzer (:ddkilzer)]

Note that when reproducing this, it's best to do the following:

1. Open Safari.
2. Empty the cache (Cmd-Alt-E).
3. Load the original URL or the attachment 12022 [details] URL.

When running shipping Safari, the messages will appear in the console.log (in the Console application).  If running a locally-built WebKit using the run-safari script, it will appear on stdout (or stderr?) from that command.

[David Kilzer (:ddkilzer)]

Attachment 12059 [details] and Attachment 12060 [details] from Bug 11999 also exhibit this behavior and print out additional error messages:

tiff data provider: Error fetching data for field "ICC Profile".