I was wondering if anybody else encountered this, I'm writing a proxy system at the moment in Go and as part of my testing I wrote some saturation tests that set up 100 connections then try to spam as much data through the connections as possible.
I did my first run of this on my Mac this morning and very quickly the processes stopped responding.. I could see them all flagged as 'stuck', they couldn't be killed and then I noticed Safari, Mail and anything else that had an active network connection was also stuck. Anything new trying to create a network connection also got stuck and couldn't be killed and clicking the Network tab of Activity Monitor just resulted in a beachball and that getting also stuck.
The box couldn't be rebooted normally and had to be power cycled to get it back up and running.
The log was filling up with this message it seems...
kernel: ctl_enqueuedata: m_allocpacket_internal(20) failed
So, just wondering if anybody has seen this themselves..?
I had to move my testing to FreeBSD (which is actually the target environment for this piece of code anyway) and it was able to run it without destabilising the network stack even when run as root and the connection limit increased to 10,000.
I did my first run of this on my Mac this morning and very quickly the processes stopped responding.. I could see them all flagged as 'stuck', they couldn't be killed and then I noticed Safari, Mail and anything else that had an active network connection was also stuck. Anything new trying to create a network connection also got stuck and couldn't be killed and clicking the Network tab of Activity Monitor just resulted in a beachball and that getting also stuck.
The box couldn't be rebooted normally and had to be power cycled to get it back up and running.
The log was filling up with this message it seems...
kernel: ctl_enqueuedata: m_allocpacket_internal(20) failed
So, just wondering if anybody has seen this themselves..?
I had to move my testing to FreeBSD (which is actually the target environment for this piece of code anyway) and it was able to run it without destabilising the network stack even when run as root and the connection limit increased to 10,000.