New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latex to PDF hangs when using Markdown tables (Origin: bugzilla #741100) #5686

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2014-12-04 07:44:56 +0000, wrote:

Created attachment 292116
Example how to reproduce the bug


pdflatex hangs (CPU goes to 100%) when creating PDF out of latex code generated by doxygen.
After several tests I isolated the problem to the usage of Markdown tables inside the doxygen comments used to document source code. Of course, MARKDOWN_SUPPORT is set to YES.

How to reproduce (see attachment for example code and config files):

Step 1: Use Markdown tables in your documentation
Step 2: Run doxygen and generate latex output
Step 3: Run make.bat found in your latex output folder (default: /latex/make.bat)
Step 4: Open Task Manager to "kill" pdflatex.exe process

Operating system: Windows 7
Doxygen version: 1.8.8
pdflatex version: MiKTeX-pdfTeX 2.9.4902 (1.40.14) (MiKTeX 2.9)

Additional info: HTML output is not affected.

On 2014-12-04 18:20:53 +0000, albert wrote:

Problem looks like to be caused by the table in the resulting parameter table.
In case Markdown is not used the "table" is just plain text (which is of course not the intention of placing the table.

On 2014-12-23 18:36:31 +0000, Dimitri van Heesch wrote:

This is a variation of bug 732768.

I hadn't realized @param and friend produce a table on their own, so adding a table there, should be treated specially; i.e. as a nested table, where one cannot use xtabular.

Should be fixed in the next GIT update.

On 2014-12-25 16:02:57 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.9. 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 (preferrably in the form of a self-contained example).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment