Error: Could not find MIME for Buffer <null> #775

codan84 · 2019-08-16T07:45:00Z

This is the same as issue 643. However, the latter is closed and seems like it is dead despite people experiencing this issue still.

Expected Behavior

Jimp.read loads an image from a URL correctly.

Current Behavior

Trying to read some images from certain URLs fails, throwing Error: Could not find MIME for Buffer <null>

Failure Information (for bugs)

Whilst certain images load correctly, other consistently fail (a failing url will always fail, without exception).
Example failing URL: https://s-media-cache-ak0.pinimg.com/736x/c9/8f/e1/c98fe17dc7de72bb29c34a0c79ef5762.jpg

Trying to Jimp.read it 1000 times gives:

Called jimp.read() 1000 times.
  Failed: 1000.
  Succeeded: 0.

Steps to Reproduce

Repo with a simple script to reproduce the error: https://github.com/codan84/jimp-bug

Context

Jimp Version: 0.6.4
Operating System: OSX 10.14.3
Node version: v10.16.2

Failure Logs

{ Error: Could not find MIME for Buffer <null>
    at Jimp.parseBitmap (/Users/gruszd01/workspace/jimp-bug/node_modules/@jimp/core/dist/utils/image-bitmap.js:108:15)
    at Jimp.parseBitmap (/Users/gruszd01/workspace/jimp-bug/node_modules/@jimp/core/dist/index.js:498:32)
    at /Users/gruszd01/workspace/jimp-bug/node_modules/@jimp/core/dist/index.js:440:15
    at /Users/gruszd01/workspace/jimp-bug/node_modules/@jimp/core/dist/index.js:168:14
    at /Users/gruszd01/workspace/jimp-bug/node_modules/@jimp/core/dist/request.js:56:9
    at IncomingMessage.<anonymous> (/Users/gruszd01/workspace/jimp-bug/node_modules/phin/lib/phin.compiled.js:1:2100)
    at IncomingMessage.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19) methodName: 'constructor' }

The text was updated successfully, but these errors were encountered:

codan84 · 2019-08-16T08:54:30Z

It's also worth mentioning that reading the same image using an external request library (I used axios) into a buffer and then loading that same image to jimp from a buffer works.
An example of that is in use-axios branch of the repo I linked above.
This would only mean that there's an issue with whatever is used for http requests in jimp...

Not working:

jimp.read(failingImageUrl)

Working:

axios({
    method: 'get',
    url: failingImageUrl,
    responseType: 'arraybuffer'
  })
  .then(function ({data: imageBuffer}) {
    return jimp.read(imageBuffer)
  })

FridayJew · 2019-08-16T17:41:48Z

Have same problem. Problematic images downloaded on local disk with requst module make this error in jimp too. But are not have visible promplems.

FridayJew · 2019-08-19T19:23:21Z

I try use GM for edited this images. It don't read them too. Show this error:
Error: Command failed: gm composite: Improper image header
If i give created by me 100% good images , he dont worked.
Maybe i did something wrong , but if i use good images with JIMP, i have wanting results.

How i can get images from internet and use them with JIMP without errors ?

lucafaggianelli · 2019-09-04T08:54:30Z

I'm facing the same issue using node-vibrant, a library that uses Jimp and the axios trick is working like a charm!

SaWey · 2019-09-04T10:15:02Z

This is happening when the image requested has a redirect response.
Your sample image is returning this response:
https://s-media-cache-ak0.pinimg.com/736x/c9/8f/e1/c98fe17dc7de72bb29c34a0c79ef5762.jpg

accept-ranges: bytes
content-length: 0
date: Wed, 04 Sep 2019 10:02:45 GMT
location: https://i.pinimg.com/736x/c9/8f/e1/c98fe17dc7de72bb29c34a0c79ef5762.jpg
retry-after: 0
status: 301
vary: Origin
x-cdn: fastly

jimp does not handle this, neither does phin <3.1.0
Either upgrading the phin library ( #ethan7g/phin#20) or handling this in the jimp core 'loadFromURL' should do the trick.

For now, I updated this code in 'core/dist/index.js to solve my problem:

function loadFromURL(options, cb) {
  (0, _request.default)(options, function (err, response, data) {
    if (err) {
      return cb(err);
    }

    if(response.headers.hasOwnProperty('location') ){
      options.url = response.headers['location'];
      return loadFromURL(options, cb);
    }

    if (_typeof(data) === 'object' && Buffer.isBuffer(data)) {
      return cb(null, data);
    }

    var msg = 'Could not load Buffer from <' + options.url + '> ' + '(HTTP: ' + response.statusCode + ')';
    return new Error(msg);
  });
}

hipstersmoothie · 2019-09-06T15:48:07Z

Please make a PR so we can all benefit from your code :) A comment helps very few but a PR can help many

@SaWey

FridayJew · 2019-09-06T19:34:07Z

jimp does not handle this, neither does phin <3.1.0
Either upgrading the phin library ( #ethanent/phin#20) or handling this in the jimp core 'loadFromURL' should do the trick.

But what i can't use downloaded images from this urls. Are not looking broken or something. Opened with any program for images viewer.

Fixes jimp-dev#775

SaWey · 2019-09-10T07:53:14Z

Please make a PR so we can all benefit from your code :) A comment helps very few but a PR can help many

@SaWey

Since there were 2 options I didn't know what way to go, but I have created a pull request which allows following redirects without upgrading phin.

hipstersmoothie · 2019-09-12T16:13:00Z

If phin supports this in a later version it think it makes sense to upgrade

SaWey · 2019-09-13T07:28:19Z

It probably does make sense, but it also makes sense to always follow redirects by default.
Phin >=3.1.0 requires the flag followRedirects to be set in order to follow redirects.

* Follow redirects Fixes #775 * Follow redirects Fixing lint error * Follow redirects Fix tests * Added redirect test * Fixed lint errors * Skip redirect test in browser as we cannot mock a server * Different test for browser * Fixed browser detection

hipstersmoothie · 2019-11-26T23:19:41Z

🚀 Issue was released in v0.9.3 🚀

hipstersmoothie · 2019-11-26T23:19:44Z

🚀 Issue was released in v0.9.3 🚀

ajeetku · 2020-02-14T08:31:58Z

Getting same in still now

Node 13.8.0
NPM 6.13.6
jimp: ^0.93

{ Error: Could not find MIME for Buffer
at Jimp.parseBitmap (../node_modules/@jimp/core/dist/utils/image-bitmap.js:106:15)
at Jimp.parseBitmap (../node_modules/@jimp/core/dist/index.js:521:32)
at new Jimp (../node_modules/@jimp/core/dist/index.js:474:13)
at _construct (../node_modules/@babel/runtime/helpers/construct.js:30:21)
at ../node_modules/@jimp/core/dist/index.js:1016:32
at new Promise ()
at Function.Jimp.read (../node_modules/@jimp/core/dist/index.js:1015:10)
{
methodName: 'constructor'
}

natuan62 · 2020-02-17T04:34:50Z

I still get this error

Node v13.5.0
NPM v6.13.7
jimp ^0.93

Add logo error Error: Could not find MIME for Buffer <null>
    at Jimp.parseBitmap (C:\Users\burakkujakku\Documents\GIT\conect\conect-api\node_modules\@jimp\core\dist\utils\image-bitmap.js:106:15)
    at Jimp.parseBitmap (C:\Users\burakkujakku\Documents\GIT\conect\conect-api\node_modules\@jimp\core\dist\index.js:521:32)
    at C:\Users\burakkujakku\Documents\GIT\conect\conect-api\node_modules\@jimp\core\dist\index.js:463:15
    at C:\Users\burakkujakku\Documents\GIT\conect\conect-api\node_modules\@jimp\core\dist\index.js:205:14
    at C:\Users\burakkujakku\Documents\GIT\conect\conect-api\node_modules\@jimp\core\dist\request.js:66:9
    at IncomingMessage.<anonymous> (C:\Users\burakkujakku\Documents\GIT\conect\conect-api\node_modules\phin\lib\phin.compiled.js:1:2100)
    at IncomingMessage.emit (events.js:317:22)
    at endReadableNT (_stream_readable.js:1215:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  methodName: 'constructor'
}

My codes use to add logo-img to picture

Jimp.read(imgRaw)
                .then(tpl =>
                    Jimp.read(imgLogo)
                    .then(logoTpl => {
                        let axios_x = tpl.bitmap.width;
                        let axios_y = tpl.bitmap.height;
                        logoTpl.opacity(0.2);
                        return tpl.composite(logoTpl, axios_x - 134, axios_y - 86, [Jimp.BLEND_DESTINATION_OVER, 0.2, 0.2]);
                    })
                )
                .then(tpl => {
                    tpl.quality(100).write(imgExported)
                })
                .then(tpl => {
                    console.log('exported file: ' + imgExported);
                })
                .catch(err => {
                    console.error('Add logo error', err);
                })

verveguy · 2020-04-14T22:41:04Z

I'm also seeing this "Error: Could not find MIME for Buffer " error sporadically one time in about 5 or so. In my case, the images are local files (no network access involved). I'm working to extract a small test case from the larger test suite to submit for repro. Current versions of jimp 0.10.2 and node 13.12.0

weiyunpeng · 2020-05-11T08:44:33Z

I'm also seeing this "Error: Could not find MIME for Buffer " error. the images are buffers.

verveguy · 2020-05-17T14:35:18Z

So, after much digging and experimentation I rewrote all of my code that creates the local files and all of the invocations of jimp to process them to absolutely guarantee there was no possibility of any async race conditions or any possibility of reusing intermediate files. That appears to have resolved my issues as far as I can tell under test.

StevenVerheyen · 2020-09-10T05:14:18Z

I also face this issue.. Any news on this old issue?

garrettlove8 · 2020-09-11T10:37:39Z

Same here...
Jimp 0.16.1
Node 10.13.0

verveguy · 2020-09-13T00:58:53Z

After rewriting all of my code that calls jimp as noted above, I no longer have these problems. I believe I can now confirm that the issues I was having were race conditions between jimp code and the file system.

marty1982 · 2021-03-04T11:38:35Z

Hi all !

I'm facing the same problem with JIMP.
I have Node-red dockerized and this is what i got when i try to upload an image from URL.

Also i have this JIMP version inside my package.json file.

Any suggestions?.

Regards!

anphetamina · 2021-04-13T13:31:37Z

Facing the same issue trying to read from a local file.
JIMP version "jimp": "^0.16.1",

marty1982 · 2021-04-13T13:40:55Z

Facing the same issue trying to read from a local file.
JIMP version "jimp": "^0.16.1",

Hi !

I could upgrade the JIMP version and now i can upload the image correctly.

homerjam · 2021-04-22T11:16:52Z

I'm also getting this issue, perhaps worth re-opening?

Error: Could not find MIME for Buffer <null>
    at Jimp.call (/Users/jameshomer/Projects/fokus/node_modules/@jimp/core/src/utils/image-bitmap.js:156:15)
    at Jimp.parseBitmap (/Users/jameshomer/Projects/fokus/node_modules/@jimp/core/src/index.js:400:17)
    at new Jimp (/Users/jameshomer/Projects/fokus/node_modules/@jimp/core/src/index.js:355:12)

jakubmz · 2021-04-23T11:47:17Z

Maybe this is of help to others. I got this error and solved it in my script. In my case it was an async bug in my code. When doing batch processing I was trying to run jimp.read() on an image file that was not found, incomplete or empty at the run time.

tbanj · 2021-10-01T04:14:50Z

@codan84 your solution works for me thanks so much

cdric · 2021-11-17T14:47:34Z

I'm also having this issue while fetching a bunch of file locally! The solution from @codan84 only work as HTTP request, the axios library doesn't help otherwise.

@jakubmz , would you mind providing a excerpt of your script that show how you have been solving the async issue?

Oyinbayode · 2022-08-26T18:48:13Z

It's also worth mentioning that reading the same image using an external request library (I used axios) into a buffer and then loading that same image to jimp from a buffer works. An example of that is in use-axios branch of the repo I linked above. This would only mean that there's an issue with whatever is used for http requests in jimp...

Not working:
jimp.read(failingImageUrl)
Working:
axios({
    method: 'get',
    url: failingImageUrl,
    responseType: 'arraybuffer'
  })
  .then(function ({data: imageBuffer}) {
    return jimp.read(imageBuffer)
  })

Thank You

This worked for me

frank3stein · 2023-03-16T21:43:25Z

Instead of using axios, you can use node-fetch to turn the image into a buffer and then feed it to jimp

import fetch from "node-fetch";

      const res = await fetch(inputURL);
      // I turn the image to a buffer and then to a Jimp image, otherwise some images are not processed
      const data = await res.arrayBuffer();
      const photo = await Jimp.read(data);

This solved my issue.

bruceceng · 2023-04-13T09:16:58Z

I just had this error, and in my case the solution was simple. I was using a command line tool to generate a png from a PDF, and for some images it worked and others it broke, but it turned out I just needed to add a 1 second delay between generating the png and trying to load it. I guess the generation program finished before the png was entirely ready or something like that (after finding a fix, I did not follow up on the details).

verveguy · 2023-04-13T12:34:55Z

Further confirmation that this is a race condition.

…

On Thu, Apr 13, 2023 at 05:17 bruceceng ***@***.***> wrote: I just had this error, and in my case the solution was simple. I was using a command line tool to generate a png from a PDF, and for some images it worked and others it broke, but it turned out I just needed to add a 1 second delay between generating the png and trying to load it. I guess the generation program finished before the png was entirely ready or something like that (after finding a fix, I did not follow up on the details). — Reply to this email directly, view it on GitHub <#775 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAUCPK7AJXEMCJQHGWT773XA7ABJANCNFSM4IME63AQ> . You are receiving this because you commented.Message ID: ***@***.***>

KernelDeimos · 2023-07-18T00:39:54Z

I maintain a server that produced this issue in production 79 times within a few days on an endpoint handling file uploads (so the buffer is coming from an uploaded file). Unfortunately I can't provide any sample data since it's in production, but if there's anything I can do to help narrow down the issue please let me know. It doesn't seem to be causing us major issues (just sometimes a thumbnail doesn't show, I presume), so it's not our priority, but I'd be happy to help if I can.

hipstersmoothie · 2023-07-26T17:46:56Z

If you have a solution I have the ability to merge!

… retrieve the image from the given URL. This buffers the image data which is then given in the input argument to the Jimp.read() function. This fixes a common issue with this function when the URL is given as the input argument where it fails to retrieve the image, resulting in the error, "Could not find MIME for Buffer", see jimp-dev/jimp#775. In this link there is a suggestion to use axios to fix the issue, this suggestion has been implemented here.

FridayJew mentioned this issue Aug 25, 2019

Can Jimp return a manipulated external image URL? #779

Closed

hipstersmoothie added the bug there is a bug in the way jimp behaves label Sep 3, 2019

SaWey added a commit to SaWey/jimp that referenced this issue Sep 10, 2019

Follow redirects

f51f429

Fixes jimp-dev#775

SaWey mentioned this issue Sep 10, 2019

Follow redirects #789

Merged

4 tasks

hipstersmoothie closed this as completed in #789 Nov 26, 2019

hipstersmoothie added the released This issue/pull request has been released. label Nov 26, 2019

andreasknoepfle mentioned this issue Dec 9, 2019

Upgrade jimp to 0.9.3 dev-rsilver/plugin-react-static-images#4

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Could not find MIME for Buffer <null> #775

Error: Could not find MIME for Buffer <null> #775

codan84 commented Aug 16, 2019 •

edited

Loading

codan84 commented Aug 16, 2019 •

edited

Loading

FridayJew commented Aug 16, 2019 •

edited

Loading

FridayJew commented Aug 19, 2019

lucafaggianelli commented Sep 4, 2019

SaWey commented Sep 4, 2019

hipstersmoothie commented Sep 6, 2019 •

edited

Loading

FridayJew commented Sep 6, 2019

SaWey commented Sep 10, 2019

hipstersmoothie commented Sep 12, 2019

SaWey commented Sep 13, 2019

hipstersmoothie commented Nov 26, 2019

hipstersmoothie commented Nov 26, 2019

ajeetku commented Feb 14, 2020 •

edited

Loading

natuan62 commented Feb 17, 2020

verveguy commented Apr 14, 2020

weiyunpeng commented May 11, 2020

verveguy commented May 17, 2020

StevenVerheyen commented Sep 10, 2020

garrettlove8 commented Sep 11, 2020

verveguy commented Sep 13, 2020

marty1982 commented Mar 4, 2021 •

edited

Loading

anphetamina commented Apr 13, 2021

marty1982 commented Apr 13, 2021

homerjam commented Apr 22, 2021

jakubmz commented Apr 23, 2021 •

edited

Loading

tbanj commented Oct 1, 2021

cdric commented Nov 17, 2021

Oyinbayode commented Aug 26, 2022

frank3stein commented Mar 16, 2023 •

edited

Loading

bruceceng commented Apr 13, 2023

verveguy commented Apr 13, 2023 via email

KernelDeimos commented Jul 18, 2023

hipstersmoothie commented Jul 26, 2023

Error: Could not find MIME for Buffer <null> #775

Error: Could not find MIME for Buffer <null> #775

Comments

codan84 commented Aug 16, 2019 • edited Loading

Expected Behavior

Current Behavior

Failure Information (for bugs)

Steps to Reproduce

Context

Failure Logs

codan84 commented Aug 16, 2019 • edited Loading

FridayJew commented Aug 16, 2019 • edited Loading

FridayJew commented Aug 19, 2019

lucafaggianelli commented Sep 4, 2019

SaWey commented Sep 4, 2019

hipstersmoothie commented Sep 6, 2019 • edited Loading

FridayJew commented Sep 6, 2019

SaWey commented Sep 10, 2019

hipstersmoothie commented Sep 12, 2019

SaWey commented Sep 13, 2019

hipstersmoothie commented Nov 26, 2019

hipstersmoothie commented Nov 26, 2019

ajeetku commented Feb 14, 2020 • edited Loading

natuan62 commented Feb 17, 2020

verveguy commented Apr 14, 2020

weiyunpeng commented May 11, 2020

verveguy commented May 17, 2020

StevenVerheyen commented Sep 10, 2020

garrettlove8 commented Sep 11, 2020

verveguy commented Sep 13, 2020

marty1982 commented Mar 4, 2021 • edited Loading

anphetamina commented Apr 13, 2021

marty1982 commented Apr 13, 2021

homerjam commented Apr 22, 2021

jakubmz commented Apr 23, 2021 • edited Loading

tbanj commented Oct 1, 2021

cdric commented Nov 17, 2021

Oyinbayode commented Aug 26, 2022

frank3stein commented Mar 16, 2023 • edited Loading

bruceceng commented Apr 13, 2023

verveguy commented Apr 13, 2023 via email

KernelDeimos commented Jul 18, 2023

hipstersmoothie commented Jul 26, 2023

codan84 commented Aug 16, 2019 •

edited

Loading

codan84 commented Aug 16, 2019 •

edited

Loading

FridayJew commented Aug 16, 2019 •

edited

Loading

hipstersmoothie commented Sep 6, 2019 •

edited

Loading

ajeetku commented Feb 14, 2020 •

edited

Loading

marty1982 commented Mar 4, 2021 •

edited

Loading

jakubmz commented Apr 23, 2021 •

edited

Loading

frank3stein commented Mar 16, 2023 •

edited

Loading