Skip to main content
andrewc94999058
andrewc94999058
Participating Frequently
June 22, 2011

P: Jpg exposes bugs in QImage and ZoomBrowser

  • June 22, 2011
  • 141 replies
  • 1143 views

Since a recent upgrade to CS5 (I guess 12.0.4 and certainly the current version) JPG files I've saved take about 1000x times longer to open in Canon ZoomBrowser 6.7.2.33 (the latest version). When I say 1000x I mean 1000x. Recent jpg are taking over 30s to open a single image! I raised this with Canon sending then old and new jpg (created using an older version of CS5 and the latest) from the same CR2 file. They said:

Extracting the EXIF data from both the good and bad images we found that the JPEGInterchangeFormatLength (JpegIFByteCount) value is bigger in the bad files.
JPEGInterchangeFormatLength shows the number of bytes of JPEG compressed thumbnail data.

We believe that this higher number is causing the problem as the ZoomBrowser EX application is trying to use the EXIF data to generate the thumbnail images, and to display the files. We were able to reproduce the issue in our test environment.

We would recommend you to contact the Adobe support in order to find out if there were any related updates released in the last few weeks that possibly was installed on your computer manually or automatically.

Please can you investigate what changed recently in CS5. And how I rescue my recent jpg images that I've needed to create for my clients. If you need the images that I sent Canon for your investigation then please let me know.

    141 replies

    Show previous replies
    F
    FeedbackCommunityMember
    Inspiring
    December 31, 2011
    The only thing that I see that is poor or "poorly written" is the code that is generating the corrupted JPEG's, and the fact that the problem has gone 4 months without a fix. The problem with the other software (what you call the poorly written parsers) is one of *error correction* because they are not properly handling an error when being fed a JPEG that does not follow JPEG standards. A JPEG that has an ICC profile embedded in the thumbnail is corrupted because embedding *ANY* JFIF markers inside a thumbnail is a violation of the standards. My recommendation if you are still claiming that a JPEG with an ICC profile embedded in the thumb is not corrupted: look it up. Learn the standards. Then follow them... rather than trying to create your own.
    X
    Xander14
    Participant
    December 31, 2011
    Minor issue for some...
    Could you send those on this message board the fix when it arrives? We'll test it really well for you!
    Bill
    F
    FeedbackCommunityMember
    Inspiring
    December 31, 2011
    There is no corruption - just sometimes including the profile in the thumbnail. Yes, poorly written JPEG parsers are hitting problems -- as they do every time something minor changes in the way we write files. And yes, we've been testing a fix for a while -- but such a minor issue won't be included in a dot release and waits for the next major release.
    F
    FeedbackCommunityMember
    Inspiring
    December 31, 2011
    Chris. Any indication when you guys (Adobe) will fix the file corruption bug? It's been months and no sign of this simple fix. The very fact (above) that you are embedding an ICC profile into a thumbnail constitutes file corruption since the JPEG spec is very clear about the fact that embedded thumbnails should be a simple image stream. It is also very specific in the fact that no JFIF/app markers are allowed in that area of the JPEG stream (the thumbnail) which is why a few programs are having problems with the corruption that results from embedding an ICC profile where it doesn't belong. Canon needs to do the same thing I did in Qimage: improve the code so that embedding an ICC profile in the wrong place doesn't cause an issue... BUT Adobe needs to hold up their end too. You're still producing JPEG files that don't follow the standard. It's not surprising that some programs have various issues when encountering a non-compliant JPEG. Yes, Canon software, Qimage (already fixed), some email software, etc. could handle the aberration better, but the best solution is to fix this at the source: fix the Adobe code that is embedding ICC profiles where they clearly do not belong.
    F
    FeedbackCommunityMember
    Inspiring
    December 31, 2011
    That's good to hear. (even if indirectly)
    F
    FeedbackCommunityMember
    Inspiring
    December 31, 2011
    We keep trying to contact Canon, we send in bug reports, but we don't hear anything back. We've provided more than enough evidence to identify this as a bug in Canon's code.
    J
    jamiewednesday
    Participating Frequently
    December 31, 2011
    OK Great, do you know if this is likely to fix similar issue in APE 10 by any chance?

    "Convert & Save"? Is that something in CS5?

    I have Zoombrowser 6.7.2 installed, still Canon's latest version...
    andrewc94999058
    andrewc94999058Author
    Participating Frequently
    December 31, 2011
    Canon told me a month ago that a fix was being planned. Here's what their Canon Consumer Support told me:

    Sorry for the delay in answering your last correspondence, and thank you for the detailed report that you provided, the information you supplied to us was very useful it allowed us to use the system as you would and doing so we managed to replicate your problem.
    I then escalated this to our HQ in Europe who intern escalated it to our quality assurance in Tokyo. The carried out an investigation and have confirmed that there is an issue.
    The found out that Photoshop CS5 add an ICC profile to the thumbnail during this process which was not done in previous versions like CS4 etc. our QA division have informed us that they will implement a fix when they release the next version of software. Until then they advise us to inform you of a work around, the work around, please use the “convert and save” feature as this will not add the ICC profile to the thumbnail.

    Please check our download centre to see when the next update to the software is release which would have the fix.
    J
    jamiewednesday
    Participating Frequently
    December 31, 2011
    So, how do we get the two firms talking to each other?

    Adobe seem to be putting the ball in Canon's court and are asking us to get Canon to contact Adobe. Canon point blank say it's an Adobe issue as earlier versions are OK.

    Seems to me that given there are more than one or two Canon users out there in the big world who also use Adobe software and are going to be deeply frustrated by this. Adobe are coming across as a little more user friendly than Canon at present, so how about Adobe contacts Canon so that the two tech teams can talk to each other and sort it out?

    In the mean time, I'll pin this stream to an email to Canon and see what they come back with.
    F
    FeedbackCommunityMember
    Inspiring
    December 30, 2011
    Again, Adobe can't do a thing about the bugs in Canon's code. Adobe has investigated and found nothing wrong on our side, but we don't know the nature of the bug in Canon's code, nor can we change Canon's code.
    Adobe cannot help you fix bugs in Canon's product.
    Canon is the only company that can fix the bugs in Canon's code.
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices