On Jun 23, 2017, at 10:09 AM, Richard Hipp <d...@sqlite.org> wrote: > > Maybe Fossil needs to disable the stack and heap size limits prior to > calling exec() or fork() and then reenable the limits afterwards?
Maybe. The current design is a bit like moralizing: Fossil has selected a limit it is willing to live within, but that doesn’t mean all other programs it could potentially interact with must obey the same limits. I’ve elaborated the test program to do a binary search for the exact limit, and it’s a smidge over 4 MiB here: 4210688 bytes. _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
