On Thu, Feb 16, 2012 at 06:37:49AM -0500, Leo Razoumov wrote: > In Unix it returns pointer pointing into actual environment (should > not be modified or deallocated). In Windows, on the other hand, > fossil_mbcs_to_utf8 allocates memory via sqlite3_malloc. This memory > is not and cannot not be freed because of UNIX behavior. > It results in memory leak on Windows. Should one care?
I think the general approach in fossil is to have short-lived processes, where those kind of leaks that don't represent relevant memory usage be freed together with the process end. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
