I have a simple server process that works perfectly with IO::Socket::INET. It opens the server socket, waits for a new connection, accept()'s it, and then forks to handle it, while the parent process waits for more connections. Seems pretty standard to me.

Well, I needed to get this server working with SSL. My first thought, "Is there a module that basically wraps SSL around the INET module?" Yup, sure enough, IO::Socket::SSL

So, I make the modifications (which are relatively minimal). Things seem to be working... I was testing my client with the server in DEBUG mode for the SSL module. What I then noticed was that the debug output was getting larger with each connection. It seemed to be outputing info relevant to previous socket connections/contexts.

Well, after seeing that, I decided to check memory and see what was happening with that. And sure enough, memory usage for the main server process was going up with every connection. When I used the INET module it remained static.

So... is there a known memory leak when using IO::Socket::SSL with fork() for handling multiple connections? I thought it was strange that no example I could find used fork. I saw one that actually used inetd to handle the incoming connections. Does anyone know if using fork with IO::Socket::SSL is possible without memory leaks?

And BTW, I did RTFM... didn't come up with much that indicated what I want to do it a problem.

Thanks,
-Alex