alamb commented on issue #419: URL: https://github.com/apache/arrow-datafusion/issues/419#issuecomment-926176783
Some observations: * each stack frame of BinaryExpr::evaluate takes up 500K * If we run the test in release mode there are no problems * If we run with a larger stack frame there are no problems * there are only a few frames of the Thus my theory is that because there are so many locals created in `BinaryExpr::evaluate` (total, not in use any any one time), the debug build leaves a (unique) space for them all and thus each frame is bloated. I have prototyped fixing the stack error by splitting the `evaluate` function into several smaller ones (each with fewer variables and thus requiring less stack. I hope to have a PR up shortly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
