I'm trying to read m3u file info from mixes that are about 200 mb and it works ok when I'm reading from the file from a web server using the http:// prefix and the path to the web server and file, but when trying to read a file from the the operating system (through the browser) i get allocation size overflow on large files. I'm developing a XUL based application using XUL based web browser as my basis, and loading the file in the browser using the file:// prefix works just fine, so it doesn't seem to be a browser limitation.
//loaded from server as web page works on large files
var file = "nasa.mp3";
var jsmediatags = window.jsmediatags;
jsmediatags.read("http://192.168.1.2/"+file, {
onSuccess: function(tag) {
console.log(tag);
},
onError: function(error) {
console.log(error);
}
});
//loaded in side JS in XUL doesn't work on large files
jsmediatags.read('file://'+file, {
onSuccess: function(tag) {
console.log(tag);
},
onError: function(error) {
console.log(error)
});
I'm not sure what the difference is in the background between loading the file as file:// or http:// so i don't understand what the underlying cause is.
I'm trying to read m3u file info from mixes that are about 200 mb and it works ok when I'm reading from the file from a web server using the http:// prefix and the path to the web server and file, but when trying to read a file from the the operating system (through the browser) i get allocation size overflow on large files. I'm developing a XUL based application using XUL based web browser as my basis, and loading the file in the browser using the file:// prefix works just fine, so it doesn't seem to be a browser limitation.
I'm not sure what the difference is in the background between loading the file as file:// or http:// so i don't understand what the underlying cause is.