Randomly exits whole application during long puts to a slow server

[karjaneth]

While I'm having a really hard time nailing down the exact conditions under which this happens, it seems that when puting a lot of large files to a fairly slow server, the application using the client will just exit with no error. No exceptions are thrown, no promises are rejected, it doesn't "crash" per-se, and the exit code is always 0, but it does just exit with no warning.

Code following the put is not run, and the last thing I can do is see the exit code if I have a process.on('exit') handler. It's as if something in the library is calling process.exit(0) (which doesn't seem to be the case) or unrefing every callback (I don't know enough about node internals to know if that's possible) or something else?

Providing a debug function to the connect function seems to sometimes show the server disconnecting right before the application exits, but even then it should throw an error, not silently exit the whole node process. The symptoms are similar to this node issue from six years ago, but that has clearly been fixed.

Anyway I'm struggling to get to the bottom of this or even to reproduce it consistently; I can't see any glaring issues in the put implementation. If anyone else can see what the cause of this could be, maybe we can get it fixed in this library.

[vkarpov15]

@karjaneth did you end up finding a solution for this? I'm scratching my head trying to figure this out now as well, even stubbed out process.exit().

[karjaneth]

No I never did. It got "resolved" for us when the server in question was made to be faster/more responsive, but this problem was never dealt with. If you figure it out, please share :)

[theophilusx]

There have been sifnificant changes made in this module since this issue was originally raised. Is it still an issue with latest version e.g. 2.5.2? If not, I would like to close this issue. If it is, then some sample code would help me in being able to reproduce it for further investigation.

[vkarpov15]

I wasn't able to consistently repro this, but it seems to have gone away after we upgraded from node 6 to node 8. No objections to closing this from me.