Serious memory leak in Gideon

[raggi at cli.di.unipi.it]

Hi all, 
 
On Friday 14 February 2003 13:12, Andras Mantia wrote: 
>  I've tried to run Gideon inside Valgrind, as you've suggested. I will 
> attach the valgrind log to this mail. What I've done is to load the last 
> project, and modify a C++ file a little, then exit Gideon. At the end there 
> are no sign of memory leak, possibly because the guilty part cleans up all 
> the used memory on exit (but fails to clean up the unneeded memory during 
> typing). Look at this part of the log (which appears as soon as I quit 
> gideon, but before everything is cleaned up): 
 
hmm, maybe i've found the problem ;) 
 
the point is that the "backgroundparser" isn't very smart, i try to explain a 
bit how it works: 
 
the bg parser maintains a list of "Unit", a unit contains a 
TranslationUnitAST, that rapresent the structure of current buffer and a list 
of "problems", found while parsing. 
 
when you modify the active buffer, the bg parser compute the 
TranslationUnitAST and the list of problems and then it replace the old unit 
with the new created one.. so, if you modify the buffer it works. 
 
the problem occur when you have several files opened, because the bg parser 
maintains the "AST" for all opened files!! ;) 
 
maybe, it can be fixed using a cache, or we can remove the "AST" when you 
close the buffer. 
 
ciao robe 
 

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/