GNOME Bugzilla – Bug 770973
Tag file size double between each run
Last modified: 2016-12-29 18:45:52 UTC
Created attachment 334948 [details] minimal example showing the pb In our project using extensively tag files for cross linking, we have a dramatic increase of the size of the tag files between the runs. (First run 5.7M, then 15M for the second, 36M for the third, 150M for the fourth...) I notice that some entries are duplicated between tag files and even inside the same tag file. I join an example showing the pb. Here is what I observe with the attached example: > cd br/doxygen > doxygen dxy/A.dxy && doxygen dxy/B.dxy && doxygen dxy/C.dxy && ls -lh tags -rw-r--r-- 1 sloriot sloriot 1.6K Sep 6 22:38 A.tag -rw-r--r-- 1 sloriot sloriot 1.9K Sep 6 22:38 B.tag -rw-r--r-- 1 sloriot sloriot 3.1K Sep 6 22:38 C.tag > doxygen dxy/A.dxy && doxygen dxy/B.dxy && doxygen dxy/C.dxy && ls -lh tags total 16K -rw-r--r-- 1 sloriot sloriot 1.6K Sep 6 22:38 A.tag -rw-r--r-- 1 sloriot sloriot 4.0K Sep 6 22:38 B.tag -rw-r--r-- 1 sloriot sloriot 5.0K Sep 6 22:38 C.tag > doxygen dxy/A.dxy && doxygen dxy/B.dxy && doxygen dxy/C.dxy && ls -lh tags total 20K -rw-r--r-- 1 sloriot sloriot 1.6K Sep 6 22:38 A.tag -rw-r--r-- 1 sloriot sloriot 5.9K Sep 6 22:38 B.tag -rw-r--r-- 1 sloriot sloriot 6.9K Sep 6 22:38 C.tag > doxygen dxy/A.dxy && doxygen dxy/B.dxy && doxygen dxy/C.dxy && ls -lh tags total 24K -rw-r--r-- 1 sloriot sloriot 1.6K Sep 6 22:38 A.tag -rw-r--r-- 1 sloriot sloriot 7.9K Sep 6 22:38 B.tag -rw-r--r-- 1 sloriot sloriot 8.8K Sep 6 22:38 C.tag If I remove the namespace in the file A/file1.h, then the pb disappears.
Sorry I meant A/file0.h
Confirmed. Should be fixed in the next GIT update.
I've just tried and it is indeed working. That's really a great news! Thank you very much
Please leave it at ASSIGNED. I'll mark it as fixed when the next official release is out. Then please verify it is indeed still working.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.13. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant (preferably in the form of a self-contained example).