On 10/27/17, Johan Kuuse wrote:
>>
> Obviously, this is not a big issue unless the Fossil web server
> handles heavy traffic of big Markdown documents - which isn't its main
> purpose anyway. :-)
Even then, it isn't an issue, because the Fossil web server creates a
new process to handle each requ
On Fri, Oct 27, 2017 at 5:19 PM, Richard Hipp wrote:
> On 10/27/17, Richard Hipp wrote:
>>
>> (2) Memory leaks do not usually matter in Fossil, since each command
>> runs to completion and the process dies, leaving the OS to clean up
>> any memory. Only memory leaks inside of a loop make a diffe
