Approved: Fortect
You may come across an error message that says the ebadf error is a bad file. There are several ways to solve this problem, which we will talk about now. EBADF bad full descriptor; and this error occurs after node without JavaScript Get Trace. So, first thing I suggest is rebooting and trying again if there is anything strange on your filesystem. If the error persists, I don’t know what to tell you.
If I reload my entire application (from the browser using the reinstall button) multiple times, for example 50 reloads / 10 seconds , I get the following type of error:
events.js: 45 Arguments [1]; throw // unhandled 'error' event ^Error: EBADF, invalid file descriptor.
Looks like a bandwidth error or something, initially I had an error when I played with the HTML 5 audio API and when I downloaded the song file 10-15 times in a row I had an error, but now i found i get error even without audio api often reloading website online, safari also throws error much faster than chrome (WTF?)
I am using Node.js 0.4.8 with express + jade I am using as well as db-mysql. connected to the corresponding MySQL database module .
I still can’t find a single post on the Internet on this topic that could help, so tell me what might be causing this awesome error because it is really confusing 🙁
Jul only asked for fourteen ’11 at 4:39
52.7k
Not The Answer You Are Looking For? Search For Other Questions Using The Node.js File Descriptor Tag Or Ask Your Own Question.
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
By “reloading the application” do you mean refreshing the home url of your application in the browser, or stopping it by restarting the node.js server process? I supposehuh that in this case, regardless of whether you can reliably reproduce it, it is usually quite difficult to debug, especially since you don’t have a good stack search to find the source. But if you want to use the capture of app.error from express.js (docs you can find here) you want to keep the path of the “Bad file descriptor” error which you hopefully sometimes have to point to which one is being deleted, is it a temporary file or something else. As far as the actual reason is concerned, we can only guess as a bad descriptor file can be a very common low level error, which experts say essentially means you are causing the use of a descriptor file that is no longer in good shape. Perform this operation (for example, read a closed file manually, open a remote file, etc.).
Resolved on July 14, 2011 5:32 am.
133k
