I thought the ulimit stack value was the max stack a process could allocate (soft/hard limit), not the default size of the stack as the post seems to allude to.
Is this just a case of mongo allocating too much onto the stack instead of onto the heap (malloc)?