On Sun, Jun 17, 2012 at 09:41:20PM +0300, Baruch Burstein wrote: > I am looking through the code and see a lot of memory allocations (such as > with mprintf, and others) where the return value pointer seems to just be > discarded after use instead of freed. Why is this not a memory leak? Is it > because every run of Fossil is just a short living process, and so the > memory gets freed by the OS upon termination, which is probably true but > probably also bad practice to rely on, or is there some other reason I am > not aware of that this is fine? Or am I just not seeing the calls to > release the memory?
the short living process. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
