Node.js app crashes when sending sending blob to db2
See original GitHub issueWe are getting inconsistent errors. The app fails when we attempt to store file attachments. This issue seems very closely related to issue #141. We don’t get a lot of details in the logs but do see this come up after each crash:
ERR *** Error in `node’: double free or corruption (!prev): 0x00000000034e67e0 ***
We applied the following recommendations from issue #141:
- var ibmdb = require(‘ibm_db’); var pool = new ibmdb.Pool(); … ibmdb.open();
With these changes, we have noticed a decrease in the failure rate but it is still occurring.
Issue Analytics
- State:
- Created 7 years ago
- Comments:28 (15 by maintainers)
Top Results From Across the Web
Node Application Crash when sending request - Stack Overflow
I have been working on a Node application. When i try to run gulp on application , i am facing this error
Read more >Node - CVE - Search Results
If a gateway client application sends a malformed request to a gateway peer it may crash the peer node. Version 2.4.6 checks for...
Read more >Platform Release Notes - AppDynamics Documentation
The sample application includes Java, Node.js, and Database Monitoring components, and is ... Android agent should not send App Start beacon immediately.
Read more >Top 10 Most Common Node.js Developer Mistakes - Toptal
Mistake #1: Blocking the event loop. JavaScript in Node.js (just like in the browser) provides a single threaded environment. This means that no...
Read more >Free for Developers
Developers and Open Source authors now have a massive amount of services offering free tiers, but it can be hard to find them...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@bimaljha what fixed it? Would love to read the commit
@rhtpandeyIN I think you misunderstand. It was my and Sam’s conclusion after reviewing the C++ code that it has several logic bugs where it frees memory prematurely or writes past the end of the buffer. You can find some examples + potential fixes here:
bnoordhuis/node-ibm_db@77e7398 bnoordhuis/node-ibm_db@42e24c7
There was much more actually (bnoordhuis/node-ibm_db@c404381) but in that commit it’s difficult to separate bug fixes from new code.
I don’t have time to pursue this but at least now you know where to look.