-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node left hanging after read #106
Comments
Thanks for including the example 👍 I was able to reproduce locally, even on node 14, not using modules, and a (much) older version of exiftool-vendored (v10.1.0) and old version of batch-cluster (v5.9.5), so this is a long-standing bug. 😞 Here's with the current versions:
Here's with the old versions:
|
Full disclosure, my consumption of The more I look at this, the more it looks like Node.js is missing an analogous Your test exits immediately if I change ExifTool's I'll update the docs to make calling If you know of a solution, please do share, I'd be happy to add that if all existing tests also pass. |
Thanks. For anyone else that might come here, I solved this by introducing emitters and listeners to the process that utilized exiftool-vendored. So, rather than depending on |
Not sure that I understand what you're asking, but to call .end() at the end of your script, you might want to just use a import { exiftool } from "exiftool-vendored";
async function run() {
try {
const tags = await exiftool.read("IMG_06565.JPG");
console.log(tags);
} finally {
await exiftool.end();
}
}
void run() |
Initially, I thought Thanks for clarifying. I figured out I need to handle this in the calling procedures, which I noted above. |
Ah, I can see how that'd be confusing! I updated my comment above to clarify that I meant the |
Describe the bug
It seems exiftool-vendored (or one of it's dependencies) is causing node to hold / hang after a simple read of file. Also, this "hold" seems to last for about 5 mins.
To Reproduce
Expected behavior
Program should have exited immediately after completion of promise.
Environment (please complete the following information):
All latest and greatest
The text was updated successfully, but these errors were encountered: