View Ticket

View Ticket

Ticket Hash: 7e32f0c17941a8f04ae372c7de8ca97572176bab
Title: Memory leak
Status: Closed Type: Code_Defect
Severity: Minor Priority:
Subsystem: Resolution: Wont_Fix
Last Modified: 2023-01-17 17:19:54
Version Found In: current trunk
I have fixed some memory issue. And I attach it.

But all place of calling "db_get" have not been fixed yet. This is in progress.

The function "cgi_replace_parameter" simply discard old value "aPramQP[[idx]].zValue", this will result memory leak.

<hr><i>drh added on 2010-08-17 11:05:19:</i><br>
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.

<hr><i>anonymous added on 2010-08-18 02:09:24:</i><br>
If fossil will have a FastCGI version in futureļ¼Ÿ It will have a better performance, and so can serve more user.