JPEG: Unsupported marker type 0x52 [rt.cpan.org #66408]

[tonycoz]

Migrated from rt.cpan.org#66408 (status was 'open')

Requestors:

• pyro@netterra.com

Attachments:

• TWetd.jpg

From pyro@netterra.com on 2011-03-06 04:02:47
:

When opening the attached JPEG with Imager I get the error,

Unsupported marker type 0x52

This was happening with Imager 0.65 so I upgraded to 0.81 and still got
the same error. Here is my environment,

Debian 4.0 Lenny

perl -v

This is perl, v5.8.8 built for i486-linux-gnu-thread-multi

uname -a
Linux rin 2.6.18.8-xen #1 SMP Mon Aug 25 23:12:08 CDT 2008 i686 GNU/Linux

I also tried it on Debian 6.0 with Imager 0.75-1+b1 from apt but got the
same error.

perl -v

This is perl, v5.10.1 (*) built for i486-linux-gnu-thread-multi

uname -a
Linux pai 2.6.32-5-xen-686 #1 SMP Wed Jan 12 07:52:18 UTC 2011 i686
GNU/Linux

Here is some simple code that produces the error.

#!/usr/bin/perl

use Imager();

my $img=Imager->new();

my $filename=$ARGV[0];

$img->open(file=>$filename);

if ($img->errstr)
{
print $img->errstr."\n";
}

From tonyc@cpan.org on 2011-03-06 04:46:06
:

On Sat Mar 05 23:02:47 2011, pyromania wrote:
> When opening the attached JPEG with Imager I get the error,
> 
> Unsupported marker type 0x52

I'm seeing the same error in the GIMP and the libjpeg tools (djpeg).

I'm not sure it's fixable while using libjpeg.

The only reference I can see to a marker 0x52 is for JPEG 2000, which
this file isn't.

I don't expect to fix this soon.

Tony

From pyro@netterra.com on 2011-03-06 07:24:07
:

> I'm seeing the same error in the GIMP and the libjpeg tools (djpeg).
> 
> I'm not sure it's fixable while using libjpeg.
> 
> The only reference I can see to a marker 0x52 is for JPEG 2000, which
> this file isn't.
> 
> I don't expect to fix this soon.
> 
> Tony

No worries. This problem isn't a show stopper for me.

I tried Imager 0.81 built against latest libjpeg version 8.3 and got the
same result. Should I send this bug to the libjpeg group and see what
they have to say?

From tonyc@cpan.org on 2011-03-07 07:15:59
:

On Sun Mar 06 02:24:07 2011, pyromania wrote:
> > I'm seeing the same error in the GIMP and the libjpeg tools (djpeg).
> > 
> > I'm not sure it's fixable while using libjpeg.
> > 
> > The only reference I can see to a marker 0x52 is for JPEG 2000, which
> > this file isn't.
> > 
> > I don't expect to fix this soon.
> > 
> > Tony
> 
> No worries. This problem isn't a show stopper for me.
> 
> I tried Imager 0.81 built against latest libjpeg version 8.3 and got the
> same result. Should I send this bug to the libjpeg group and see what
> they have to say?

You could try, though they might just consider it a corrupt file.

There are documented mechanisms for applications to add extra content to
JPEG images, if someone decided to use an unused marker type then it's
not a valid JFIF/JPEG file.

Where did the file come from?

Tony

From tonyc@cpan.org on 2011-08-08 09:57:21
:

An idea for fixing this:

Imager uses the io_layer mechanism which has callbacks for retrieving
data from the file ( or buffer, etc).

An intermediate layer could be added that parsed JFIF/JPEG blocks and
either discarded or replaced unsupported markers.

Still low priority.

Tony