On Dec 28, 2017, at 9:11 AM, Richard Hipp <d...@sqlite.org> wrote: > > On 12/28/17, Warren Young <war...@etr-usa.com> wrote: >> >> drh, I seem to recall messages about non-free()’d buffers in the Fossil >> server code, where the patch was rejected with the argument that the forked >> child is about to die anyway, so why bother freeing the buffer. That >> doesn’t really apply in a single-process server, as I expect applies on the >> Windows side. Will Fossil server leak memory on Windows? > > Even the Windows server starts a new process to handle each request. > It just does so using system() rather than fork().
That leaves me wondering what the threads are used for then, if not to implement a thread-per-connection model. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
