Bad socket issue after extended internet outage #118
Description
I was running with valgrind but this was producing so many messages that I lost the top of my scrollback buffer.
Internet was out for about 8 hours overnight. Haven't had a chance to dig into it yet.
==4148834== Warning: invalid file descriptor 1031 in syscall openat()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall openat()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall openat()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall openat()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
^C==4148834== Warning: invalid file descriptor 1031 in syscall openat()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
==4148834== Warning: invalid file descriptor 1031 in syscall socket()
[S] 1623021947.296124 stat.c:16 2 0 0 81 0 4 0 2
==4148834==
==4148834== HEAP SUMMARY:
==4148834== in use at exit: 8,117 bytes in 20 blocks
==4148834== total heap usage: 2,137,891,816 allocs, 2,137,891,796 frees, 201,899,765,715 bytes allocated
==4148834==
==4148834== LEAK SUMMARY:
==4148834== definitely lost: 0 bytes in 0 blocks
==4148834== indirectly lost: 0 bytes in 0 blocks
==4148834== possibly lost: 0 bytes in 0 blocks
==4148834== still reachable: 8,117 bytes in 20 blocks
==4148834== suppressed: 0 bytes in 0 blocks
==4148834== Rerun with --leak-check=full to see details of leaked memory
==4148834==
==4148834== For lists of detected and suppressed errors, rerun with: -s
==4148834== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==4148834== could not unlink /tmp/vgdb-pipe-from-vgdb-to-4148834-by-root-on-???
==4148834== could not unlink /tmp/vgdb-pipe-to-vgdb-from-4148834-by-root-on-???
==4148834== could not unlink /tmp/vgdb-pipe-shared-mem-vgdb-4148834-by-root-on-???