Doxgen 1.7.5 on Win7 x64 crashes (Origin: bugzilla #656642)

[doxygen]

status RESOLVED severity blocker in component general for ---
Reported in version 1.7.5 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

• Surpac_1.7.5.Doxyfile (ID 194099)
• Surpac.Doxyfile (ID 194183)

On 2011-08-16 11:14:30 +0000, Max wrote:

Using doxygen 1.7.5 on win7 x64 SP1 to document Freescale's MQX RTOS library.

Doxygen crashes each and every time with the following error (Visual Studio 2010 debuger): "Unhandled exception at 0x004ecdbf in doxygen.exe: 0xC0000005: Access violation reading location 0x00000048."

The last message displayed at console is:
.
.
.
Resolving citations...
Generating citations page...
Counting data structures...
Resolving user defined references...
Finding anchors and sections in the documentation...
Combining using relations...
Adding members to index pages...

After doxygen.exe crashes, it leaves a temp file of about 96MB in destination folder.

Hope the above helps, otherwise please feel free to contact me by email.

Regards,
Max.

On 2011-08-16 11:52:47 +0000, Dimitri van Heesch wrote:

I have some additional questions:

Can you describe a way for me to reproduce the problem?
(can I get the sources somewhere and what configuration file did you use?)

Did you build doxygen yourself or did you install the default package?
(if you build it yourself can you provide a stack trace?)

Did/does it work with version 1.7.4?

Does it also crash on a 32 bit version of Windows?

On 2011-08-18 04:54:10 +0000, Andy Dent wrote:

Created attachment 194099
Config file for runs crashing Doxygen on 1.7.5

On 2011-08-18 05:26:32 +0000, Andy Dent wrote:

I installed the default package and am getting the same crashes on Windows7 x64. Will try to dig out a test VM 32bit machine to run it on and can also test Vista x64.

The code base is a very large one, about 1 million lines C++ but has had no problems with Doxygen in at least the last year inc running 1.7.4.

Doxywizard reliably shows the same crash point:

Resolving citations...
Generating citations page...
Counting data structures...
Resolving user defined references...
Finding anchors and sections in the documentation...
Combining using relations...
Adding members to index pages...
**** CRASH HERE ******

I re-installed 1.7.4 and it runs fine on the same source with the same config file.

On 2011-08-18 06:51:23 +0000, Andy Dent wrote:

I had the idea that it might be due to the files being excluded but taking the exclusion clause out of the settings file and removing them had no effect.

On 2011-08-18 07:16:02 +0000, Dimitri van Heesch wrote:

Hi Andy,

I did find one issue in the meantime that could lead to a crash. I've fixed it and made a test version available here:

ftp://ftp.stack.nl/pub/doxygen/test/doxygen-1.7.5-20110817-setup.exe

Can you try it and let me know if it fixes your problem?

On 2011-08-18 08:40:39 +0000, Max wrote:

The patch 1.7.5-20110817 fixed the problem for me. Tried it several times with different settings an no problem anymore at all.

Thanks.

On 2011-08-18 08:41:19 +0000, Max wrote:

.

On 2011-08-18 14:49:44 +0000, Dimitri van Heesch wrote:

Andy, can you still let me know if the test version also works for you?
I'm considering a bug fix release, but if it doesn't also fix your crash then it needs more work first.

On 2011-08-19 05:01:11 +0000, Andy Dent wrote:

Created attachment 194183
config file ran OK with patched Doxygen 1.7.5

This is the file I was using with 1.7.4 previously and differs from a crashing one only in the comments so may be a red herring.

On 2011-08-19 05:15:15 +0000, Andy Dent wrote:

Using the patched version got further but still crashed with my original config file attached earlier.

Counting data structures...
Resolving user defined references...
Finding anchors and sections in the documentation...
Combining using relations...
Adding members to index pages...
Generating style sheet...
Generating index page...
Generating page index...
Generating example documentation...
Generating docs for example To...
Generating file sources...
Generating code for file D:/Build/BDSL_13_15/ssiutil/ConversionFunctions.cpp...
Generating code for file D:/Build/BDSL_13_15/ssiutil/ConvertCP1251.cpp...
Generating code for file D:/Build/BDSL_13_15/ssiutil/ConvertHPRoman8.cpp...
Generating code for file D:/Build/BDSL_13_15/ssiutil/ConvertNative.cpp...
Generating code for file D:/Build/BDSL_13_15/ssiutil/ConvertUTF.cpp...
Generating code for file D:/Build/BDSL_13_15/ssiutil/ConvertUTF.h...
Generating code for file D:/Build/BDSL_13_15/ssiutil/DataBuffer.cpp...
Generating code for file D:/Build/BDSL_13_15/ssiutil/diag.cpp...
Generating code for file D:/Build/BDSL_13_15/ssiutil/GeneralUtils.cpp...
****** crash

Problem signature:
Problem Event Name: APPCRASH
Application Name: doxygen.exe
Application Version: 0.0.0.0
Application Timestamp: 4e4bb90e
Fault Module Name: doxygen.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4e4bb90e
Exception Code: c0000005
Exception Offset: 000119ca
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

However, when I ran it with my pure 1.7.4 file now attaached surpac.doxyfile, it seemed to run OK. The logfile from that run is nearly 220MB and the Doxywizard program was unresponsive whilst running.

On 2011-08-19 08:07:10 +0000, Dimitri van Heesch wrote:

Hi Andy,

Sorry to hear doxygen still crashes.

I've found some additional issues that could potentially crash doxygen.
I've fixed them, and made a newer test version available here (note this is only the doxygen.exe but it does it was build with debug symbols).

ftp://ftp.stack.nl/pub/doxygen/test/doxygen.exe-1.7.5-20110819.zip

Please let me know if you get any further with this build.

On 2011-08-21 08:19:47 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5.1. 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.