Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Congratulations, you successfully breached the first of 9 NCIS main frame firewalls.
Yes. I do remember this NCIS episode where the NCIS chief was led by the NCIS hackerman to prevent the NCIS from being hacked by a botnet.
A countdown had shown the remaining time till every bit of data would be erased forever since there is no backup system.
xD
Just got this slack from our server admin.
When there are only 2 pages on Google you know you're in serious shit.
So I'm making a file uploader for a buddy of mine and I got an error that I had never seen before. Suddenly I had C++ code and some other weird shite in my terminal. Turns our that I got a memory leak and the first thing that sprung to mind was "Fuck yes, I get to do some NCIS ass debugging".
Now the app worked fine for smaller files, like 5MB - 10MB files, but when I tried with some Linux ISO's it would produce the memory leak.
Well I opened the app with --inspect and set some breakpoints and after setting some breakpoints I found it. Now, for this app I needed to do some things if the user uploads an already existing file. Now to do that I decided to take the SHA string of the file and store it in a database. To do this I used fs.readFile aaaaaaaaaand this is where it went wrong. fs.readFile doesn't read the file as a stream.
Well when I found that, boy did I feel stupid :v
rant
nodejs
memory leak
debugging
whoops