> Thanks! It has been committed. I doubt though if the Go runtime uses > libc malloc.
I don't know if the pure Go runtime uses libc malloc. However, some of the test code involves cgo and calls into various C libraries including libcrypto. So it definitely exercised malloc in a threaded environment.
