Hello,
I have a thread running (OS X 10.10.5) that hangs with this stack trace. It’s after about 20 hours of operation, I think it might be related to a low memory condition. But, the question is, why doesn’t malloc
just return null? Why does the execution of the thread need to halt? The actual number of bytes requested is small (for a string operation).
1 operator new(unsigned long) + 37 (libc++abi.dylib + 124485) [0xa0339645] 2
1 malloc + 29 (libsystem_malloc.dylib + 3997) [0xa1829f9d] 2
1 malloc_zone_malloc + 116 (libsystem_malloc.dylib + 7243) [0xa182ac4b] 2
1 default_zone_malloc + 3 (libsystem_malloc.dylib + 67909) [0xa1839945] 2
*1 thread_exception_return + 0 (kernel + 632362) [0xffffff800029a62a] (runnable) 2
Thank you for your insights.
Michael Domino
Direct: +1.617.816.5851
http://www.spirion.com
(formerly Identity Finder)
641 Lexington Avenue, 13th floor, New York, NY 10022