Fossil is a command-line tool that runs a single task (quickly) and then exits.
Memory leaks, as long as they do not occur inside a loop, are harmless and
unimportant.  Memory leaks of 40 or 50 bytes that are limited in number are
particularly unimportant and should be ignored.

Do any of these leaks you identify consume large amount of memory (megabytes)
or can any of them occur an unbounded number of times depending on the size
of the repository or other input factors?  If so, please let us know and we
will have a look.  Otherwise, this is not a problem and is not something
we intend to fix.

Thanks for the report.