Browsers can’t handle that many arguments. See this snippet for example: alert.apply(window, new Array(1000000000)); This yields RangeError: Maximum call stack size exceeded which is the same as in your problem. To solve that, do: var arr = []; for(var i = 0; i < 1000000; i++){ arr.push(Math.random()); }
From “Intel®64 and IA-32 Architectures Optimization Reference Manual”, section 4.4.2: “For best performance, the Streaming SIMD Extensions and Streaming SIMD Extensions 2 require their memory operands to be aligned to 16-byte boundaries. Unaligned data can cause significant performance penalties compared to aligned data.” From Appendix D: “It is important to ensure that the stack frame … Read more
From node –help: node –max-stack-size=val Update: as the comments indicate, even though the help text still lists the –max-stack-size option, in node v0.10.x you need to use –stack-size instead. node –stack-size=val
There is no such API provided by the JVM— even for agents started with -javaagent. The JVM TI is a native interface provided for native agents started with the -agent option or for debuggers. Java agents might use the Instrumentation API which provides the lowlevel feature of class instrumentation but no direct profiling capability. There … Read more
You can do this with a trace function (props to Spacedman for improving the original version of this to trace returns and use some nice indenting): def tracefunc(frame, event, arg, indent=[0]): if event == “call”: indent[0] += 2 print(“-” * indent[0] + “> call function”, frame.f_code.co_name) elif event == “return”: print(“<” + “-” * indent[0], … Read more
I think primarily you’re getting confused between a program’s stack and any old stack. A Stack Is an abstract data structure which consists of information in a Last In First Out system. You put arbitrary objects onto the stack and then you take them off again, much like an in/out tray, the top item is … Read more
To disable these, use the gcc option -fno-asynchronous-unwind-tables -fno-dwarf2-cfi-asm may be needed also.
The call stack could also be called a frame stack. The things that are stacked after the LIFO principle are not the local variables but the entire stack frames (“calls”) of the functions being called. The local variables are pushed and popped together with those frames in the so-called function prologue and epilogue, respectively. Inside … Read more
I believe the problem is that your array is on the stack, and that your compiler is too old to support over-aligned stack variables. GCC 4.6 and later fixed that bug. C11/C++11 alignas(64) float a[4]; Just Works for any power of 2 alignment. So does the GNU C __attribute__((aligned(x))) as you were using it. (In … Read more
You should wrap your recursive function call into a setTimeout, setImmediate or process.nextTick function to give node.js the chance to clear the stack. If you don’t do that and there are many loops without any real async function call or if you do not wait for the callback, your RangeError: Maximum call stack size exceeded … Read more