You might be agreeing without realising it. >> I would argue that the title is misleading and overly alarmist here. This particular bug may have involved recur

You might be agreeing without realising it. >> I would argue that the title is misleading and overly alarmist here. This particular bug may have involved recursion and a stack overflow, but that's like saying "malloc kills" in the title of an article about a heap overflow bug. Let's see what the article[1] you cited says: Rule 3: Do not use dynamic memory allocation after initialization. Rationale: This rule appears in most coding guidelines for safety-critical software. The reason is simple: Memory allocators, such as malloc, and garbage collectors often have unpredictable behavior that can significantly impact performance. If you think recursion is a known security problem, do you also think using the heap is a known security problem?