You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 16, 2020. It is now read-only.
Hi,
when analyzing files with e.g. 0kb or files that Mediainfo dont support like a json fie, i am getting a crash of my module which i cannot even catch by using try/catch.. Thats bad because my webserver should always be running...
RangeError [ERR_OUT_OF_RANGE]: The value of "start" is out of range. It must be >= 0 and <= 2 ** 53 - 1. Received -1
at checkPosition (internal/fs/streams.js:45:11)
at new ReadStream (internal/fs/streams.js:83:5)
at Object.createReadStream (fs.js:1802:10)
at ReadStream. (C:\dev\ffastrans_webui\rest_service\node_modules\node-mediainfo\dist\index.js:84:50)
I was able to workaround by using this code in line 82 in index.js - this way i get some result from mediainfo and if it is just the file size then so be it... all better than a crash that i cannot catch...
if (seekTo < 0){
seekTo = 0;
}
Now i fear that there could be more issues that cause a crash of my application, any idea how i can catch an error thats thrown in the wasm?
Hi,
when analyzing files with e.g. 0kb or files that Mediainfo dont support like a json fie, i am getting a crash of my module which i cannot even catch by using try/catch.. Thats bad because my webserver should always be running...
RangeError [ERR_OUT_OF_RANGE]: The value of "start" is out of range. It must be >= 0 and <= 2 ** 53 - 1. Received -1
at checkPosition (internal/fs/streams.js:45:11)
at new ReadStream (internal/fs/streams.js:83:5)
at Object.createReadStream (fs.js:1802:10)
at ReadStream. (C:\dev\ffastrans_webui\rest_service\node_modules\node-mediainfo\dist\index.js:84:50)
I was able to workaround by using this code in line 82 in index.js - this way i get some result from mediainfo and if it is just the file size then so be it... all better than a crash that i cannot catch...
Now i fear that there could be more issues that cause a crash of my application, any idea how i can catch an error thats thrown in the wasm?