View Issue Details

IDProjectCategoryView StatusLast Update
0006564JEDI VCL00 JVCL Componentspublic2019-03-20 08:55
ReportersenderAssigned Toobones 
Status resolvedResolutionfixed 
Product VersionDaily / GIT 
Target VersionFixed in VersionDaily / GIT 
Summary0006564: JvDBImage shows "Bitmap image is not valid" to some kind of jpeg image.
DescriptionSome kind of jpeg image does not has the "JFIF" or "Exif" signature at stream offset 6 as procedure GraphicSignaturesNeeded expected.
Steps To ReproduceThe attached picture is the header dump of the jpeg file. The jpeg picture is private so I can't upload it.
Additional InformationSimple workaround is to add:

    RegisterGraphicSignature([$FF, $D8], 0 , TJPEGImage);


procedure GraphicSignaturesNeeded;

But I think we should add file ending signature examination since a valid jpeg file is always ended with 0xFF, 0xD9. (According to
TagsNo tags attached.


2017-04-09 11:42


file header.png (42,399 bytes)
file header.png (42,399 bytes)


2017-07-02 08:44

reporter   ~0021429

1. can this particular JPEG file provided for further analysis?
2. what do other image processing applications say when you try to load this image in them?

2017-07-10 02:57


header.jpg (28,773 bytes)
header.jpg (28,773 bytes)


2017-07-10 03:02

reporter   ~0021432

I have uploaded the jpeg file, please check the attached file "header.jpg".

I have tried lots of graphic processing applications, including IrfanView,, GIMP, Corel PaintShop pro, Adobe Photoshop. They all can open this file without problem.


2018-07-18 15:55

administrator   ~0021526

Could you check if the issue is still present in the latest GIT content? If yes, please provide the zipped sources of an application showing this.

2018-07-25 05:58


JvDBImageInvalidImage.7z (129,355 bytes)


2018-07-25 06:07

reporter   ~0021567

The problem is still there.

I have uploaded demo source package which contains 2 demo programs. The one which includes my patched JvJVCLUtils.pas can show the jpeg file in mdb. The unpatched one will show "Unsupported stream format".

To use the demo program, just compile and run, then pressed the "open db" button.


2019-03-11 22:14

reporter   ~0021638

So you know how to put your modification into a GitHub pull request? If yes, can you do this?


2019-03-15 06:35

reporter   ~0021649

Pull request is created. Please check GitHub for it.


2019-03-19 19:57

reporter   ~0021651

It already has been merged in, but I don't have permission to change the status of this mantis issue. Otherwise I would declare this as resolved. Thanks for creating the pull request.

Issue History

Date Modified Username Field Change
2017-04-09 11:42 sender New Issue
2017-04-09 11:42 sender File Added: file header.png
2017-07-02 08:44 mh Note Added: 0021429
2017-07-10 02:57 sender File Added: header.jpg
2017-07-10 03:02 sender Note Added: 0021432
2018-07-18 15:55 obones Note Added: 0021526
2018-07-18 15:55 obones Status new => feedback
2018-07-25 05:58 sender File Added: JvDBImageInvalidImage.7z
2018-07-25 06:07 sender Note Added: 0021567
2018-07-26 11:07 obones Status feedback => acknowledged
2019-03-11 22:14 mh Note Added: 0021638
2019-03-15 06:35 sender Note Added: 0021649
2019-03-19 19:57 mh Note Added: 0021651
2019-03-20 08:55 obones Status acknowledged => resolved
2019-03-20 08:55 obones Fixed in Version => Daily / GIT
2019-03-20 08:55 obones Resolution open => fixed
2019-03-20 08:55 obones Assigned To => obones