#12022: BUG: port doesn't release (any?) memory ------------------------------+--------------------------------------------- Reporter: flob@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.4.42 Keywords: port memory leak | Port: ------------------------------+--------------------------------------------- Changes (by jmr@…): * cc: pguyot@… (added) Comment: I've narrowed down the memory usage problems to the filemap code. It adds about 160 MB to port's RPRVT each time it is used on my system. To demonstrate, open up port in interactive mode, run the activate, deactivate, provides or contents target, and watch your free memory disappear. Note that it's far worse on trunk because it now closes the filemap when it's done with it (so more memory gets allocated next time it's opened). Upon closing, the variable is unset, FreeFilemapInternalRep() is called, and the ref count goes to zero, but no memory seems to be freed up. -- Ticket URL: <http://trac.macports.org/ticket/12022#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS