4 ms·
Yes, it ought to be. I can hardly see that as a "bug" in Linux. Clearly, allocating 20k stack variables can't be right and the bug is on Google's side. The sta
by mike_hock 3y ago
Yes, it ought to be. I can hardly see that as a "bug" in Linux. Clearly, allocating 20k stack variables can't be right and the bug is on Google's side.
The stack isn't for bulk storage, I thought that was common knowledge.
- veave 3y agoIf a javascript program crashes the interpreter that is a bug in the interpreter. I don't understand how this is even a discussion. In the era of IE6 there were lots of one-liners that could crash the browser and no one would blame whoever wrote them.
- mike_hock 3y agoIn the interpreter, yes, not the kernel that enforces a reasonable stack limit.
- realitythreek 3y agoIt had already been fixed in the kernel. Linus tends to agree with it being a bug.
- AshamedCaptain 3y agoIts even worse, since they are not increasing the stack pointer and thus firefox is violating some redzone abi somewhere.