06.06.2011, 13:10
Hi guys,
I am currently reading through ******' code optimisation topics, to help with optimising a 30k line game mode. One problem we are unable to get rid of is the stack memory error:
Stack/heap size: 16384 bytes; estimated max. usage: unknown, due to recursion
As I understand it, this is caused by a function calling itself and creating new variables each time. Looking through the code, I can't seem to see any functions directly calling themselves, but I assume the same would happen if it was indirectly calling itself, through another function?
My question is is there a way to trace this, as it is quite difficult to find in the 30k lines of code where it is happening.
Thanks.
I am currently reading through ******' code optimisation topics, to help with optimising a 30k line game mode. One problem we are unable to get rid of is the stack memory error:
Stack/heap size: 16384 bytes; estimated max. usage: unknown, due to recursion
As I understand it, this is caused by a function calling itself and creating new variables each time. Looking through the code, I can't seem to see any functions directly calling themselves, but I assume the same would happen if it was indirectly calling itself, through another function?
My question is is there a way to trace this, as it is quite difficult to find in the 30k lines of code where it is happening.
Thanks.