That was the leak—now it crashes!

A small recap to the memory leak from last week [1]. Yes, that was the leak [2] and the server in question has been steady in memory usage since. In addition to that, I fixed an issue with a custom module in my gopher server [3] where I neglected to close a file. It wasn't a leak per se, as the files would be closed eventually but why keep them open due to some sloppy programming?

But now a new problem has cropped up—the formerly leaking program is now crashing. Hard! It's getting an invalid pointer, so off to track that issue down …

Sigh.

[1] /boston/2020/04/22.1

[2] /boston/2020/04/23.1

[3] https://github.com/spc476/port70

Gemini Mention this post

Contact the author