Re: [Doxygen-users] Doxygen 1.8.6 unusable to build our doc due to tag_files generated
Brought to you by:
dimitri
From: Sebastien L. (GeometryFactory) <slo...@gm...> - 2014-03-01 14:02:47
|
On 02/28/2014 10:33 PM, Dimitri van Heesch wrote: > Hi Sebastien, > Hi Dimitri, > On 28 Feb 2014, at 10:59 , Sebastien Loriot <slo...@gm...> wrote: > >> Hello, >> >> Our library documentation is decomposed into packages and each package >> documentation has its own doxygen compilation unit. The links between >> the packages are handled thanks to the tag-files. >> The build is OK when using doxygen 1.8.4. >> >> When we tried to switch to 1.8.6 we noticed that the second build >> (the first build generates the tag-files) allocates huge amounts of >> memory making the computer swapping and unusable. >> If I use doxygen 1.8.4 for the second build (i.e. using tag-files from >> doxygen 1.8.6), the behavior is the same. >> >> I tried to make a small reproducible test case without success. >> One of our developer suspects this commit 31198c21. >> >> Is it a known issue? >> If this can help, I can find out what in the diff of the tag-files >> cause the issue. What I quickly notice in the diff are: >> -change in anchor hash >> -extra <type>@</type> in enums >> -more members and class are exported > > > It is not a known issue, and I would like to understand better what is causing this. > Some things to get clear first: > - are you using the latest from GitHub or the standard 1.8.6 release? > - is doxygen eating all memory and hanging indefinitely/crashing when out of memory, or > just using more memory but finally finishing just fine? > - if you generate the tag files with version 1.8.4, does the second run then work with 1.8.6? > I just tried with the latest git version and it seems you already have fixed the issue. I should have tried it first, sorry for the noise. Best regards, Sebastien. > Regards, > Dimitri > |