The patch at https://www.fossil-scm.org/fossil/info/6e6e4b1d26e187ed attempts to limit the amount of heap space and stack space used by Fossil as a defense against the "stack clash" bug found on many versions of Unix. There are no known attacks against Fossil using stack clash. This is a proactive change.
Stack space is limited to 2MB and heap space is limited to 1GB on 32-bit systems or 10GB on 64-bit systems. Is this enough? It seems to be working well enough on the Fossil self-hosting server. I wonder, though, of some users have repositories with very large files for which more heap space is needed. Or perhaps there are some deep recursions in Fossil that require more stack space. If there are deep recursions in Fossil, maybe they should be fixed rather than increasing the stack space. Review and criticism of this change is welcomed. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev