When I compile the following document xelatex crashes (a real windows crash with "memory error). The crash happens also when I use xelatex --no-pdf.
\documentclass{article}
\begin{document}
$\sqrt{x^1_2}$
\end{document}
From a discussion on the xetex mailing list, it looks as if other systems (mac and linux) don't have a problem (but as there are so many versions around, I can't be sure).
This is XeTeX, Version 3.1415926-2.2-0.998.3 (MiKTeX 2.7)
Ulrike Fischer
Logged In: YES
user_id=67066
Originator: NO
This is a really simple document. Unfortunately, I cannot reproduce the bug.
Logged In: YES
user_id=1562266
Originator: YES
You are not the only one who can't reproduce it ;-(. On the mailing list someone also told that is works fine on his system. My document doesn't crash if I load other mathfonts (e.g. with fourier), so it is possible that some of my tfm's are corrupted. I will try to reinstall them and if this fails too make some tracing or so and give more informations about my system.
Ulrike Fischer
Logged In: YES
user_id=1562266
Originator: YES
Reinstalling the cm-package didn't help.
I made some tests with debugview and remarked that xelatex doesn't crash when I set enough trace-options. It doesn't matter which options I set as long as I set enough (about 15). Perhaps there is a timing problem when xelatex is trying to get the fontdimens for the sub- and the superscript. I'm running miktex here on winxp professional on a quite old (and not very fast) laptop.
Ulrike Fischer
Logged In: YES
user_id=1562266
Originator: YES
Reinstalling the cm-package didn't help.
I made some tests with debugview and remarked that xelatex doesn't crash when I set enough trace-options. It doesn't matter which options I set as long as I set enough (about 15). Perhaps there is a timing problem when xelatex is trying to get the fontdimens for the sub- and the superscript. I'm running miktex here on winxp professional on a quite old (and not very fast) laptop.
Ulrike Fischer
Logged In: YES
user_id=67066
Originator: NO
I can now reproduce the issue and know where it occurs. I am not sure whether it is a MiKTeX
(or Windows) specific problem: the font_mapping array isn't initialized with zeros. After
zeroing the array (in the init routine), the crash does not occur anymore.
The fix will be made available with the next update. Please reopen this report, if it does not
solve your problem.