After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 582276 - Doxywizard crashes on exit
Doxywizard crashes on exit
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: doxywizard
1.5.8
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-05-12 07:26 UTC by 127.0.0.0
Modified: 2009-08-20 10:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description 127.0.0.0 2009-05-12 07:26:41 UTC
I am using Doxygen 1.5.8 (now 1.5.9) under Windows XP Professional for all my projects. For this reason I am using a file connection between files with .doxy ending and doxywizard. So if a double click on a file with .doxy ending doxywizard starts. However on some files doxywizard crashes if a want to exit it.

The error can be easily reproduced by creating a new file with doxywizard, storing it under C:\, closing doxywizard and reopening the file via right-click -> Open With -> Doxywizard on the doxywizard file and closing doxywizard again.

The error does not occur if the file is loaded via starting doxywizard loading the file via the File -> Open Command and closing doxywizard. It also does not occur on all storing directories. It seems that only some directory names causes / influences the crash. Furthermore, I could not see the error on a previous version (1.5.7).

In version 1.5.9 I have not seen the problem under my projects. However, the problem is still there, if you want to reproduce the error on the above mentioned way.
Comment 1 Dimitri van Heesch 2009-05-18 08:11:34 UTC
The (probable) cause for the crash has been indentified and should be fixed in the next subversion update (and thus also in the next release).
Comment 2 Dimitri van Heesch 2009-08-20 10:13:11 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.0. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).