Crash on OS X? - "pointer being freed was not allocated"

[ape-project]

Crash on OS X? - "pointer being freed was not allocated"

[dsilvers]

Maybe it's not an error with stray clients. I just tried bombarding the APE server with data (as we plan to do this with our app). Received the same error and gdb output above.

Also tried running as root. Same error.

Please let me know if there's anything else I can try. Thanks!

[jdtcdr]

I have run into this problem also and tracked it down to the fact that close_socket is not protected from trying to free the same buffer twice if called to close the same socket twice. While this double call should not be happening, I see consistently that the same fd is reported twice for read from the kevent() call which is used to implement events_poll on this platform. The simple fix is one line to clear the buffer pointer so that if close_socket is called again on the closed fd it will not attempt to free the buffer again.

Look for the free(co->buffer_in.data); line and add the line:
co->buffer_in.data = NULL;

after it.

I have put up a commit with this fix so it can be rolled into the code.
It is commit 08c6354 on jdtcdr:issue-14-pointer-freed

[lcharette]

Issue over 3 years old. Closing. Reopen a new one if issue is still there.