DRLParser keeps increasing its memory usage as its parses more files from
the source tree. I think this could be libclang compilation database
(Since we're using same index for all compiled translation units) plus all
the processed translation units we generate. Since the parser works per
header, not in a global way, maybe we should clean translation unit data
after parsing and processing.
DRLParser keeps increasing its memory usage as its parses more files from the source tree. I think this could be libclang compilation database (Since we're using same index for all compiled translation units) plus all the processed translation units we generate. Since the parser works per header, not in a global way, maybe we should clean translation unit data after parsing and processing.