# [OS X TeX] TeX capacity exceeded?

Herbert Schulz herbs at wideopenwest.com
Tue Jul 15 18:55:58 EDT 2014

```On Jul 15, 2014, at 5:47 PM, Ross Moore <ross.moore at mq.edu.au> wrote:

> Hi Herb, Gerard
>
> On 15/07/2014, at 3:31 PM, Herbert Schulz wrote:
>
>>
>> On Jul 15, 2014, at 4:47 PM, Walschap, Gerard <gerard at ou.edu> wrote:
>>
>>> I have a brand new machine running OS 10.9.4 and TeXShop 3.36.2. I tested the installation by typesetting a simple document, and everything seemed to work. When I try to typeset a book I’m writing however, it gets stuck on chapter 2. The strange thing is that I haven’t touched chapter 2 in months. Here’s the relevant (I think) part of the console log:
>>>
>>> ./Chapter2.tex:1184: TeX capacity exceeded, sorry [main memory size=5000000].
>>> \rlap #1->\hb at xt@ \z@ {#1\hss }
>>>
>>> l.1184 ... can be found for example in \cite{HS74}
>>>                                                 . The relation between int...
>
>
> Certainly an infinite loop here.
>
> Are you using any special packages for citations?
> Or any home-grown coding, related to \cite
> that is not guaranteed to be robust against changes in other packages?
>
> What happens if you run it again after a bombed-out run?
> This will have a fresh .aux  file.
> It might give a different result, at least initially; so run it
> yet again.
>
>>>
>>> ./Chapter2.tex:1184:  ==> Fatal error occurred, no output PDF file produced!
>>> Transcript written on diffgeom.log.
>>> Latexmk: Index file 'diffgeom.idx' was written
>>> Latexmk: Reference `Ex:detIsom' on page 83 undefined
>>> Latexmk: Summary of warnings:
>>> Latex failed to resolve 1 reference(s)
>>> Collected error summary (may duplicate other messages):
>>> pdflatex: Command for 'pdflatex' gave return code 256
>>> Latexmk: Use the -f option to force complete processing,
>>> unless error was exceeding maximum runs of latex/pdflatex.
>>> Latexmk: Errors, so I did not complete making targets
>>>
>>> Any suggestions? Thanks,
>
> Can you extract a minimal example that exhibits this behaviour?
>
>
>>>
>>> -Gerard
>>
>> Howdy,
>>
>> This could be caused by one of several things but I'd first guess an infinite loop of some sort. Without some more information this is very difficult to diagnose. You might try using the etex package (\usepackage{etex}) but i'm not at all sure that will help.
>>
>> Good Luck,
>>
>> Herb Schulz
>> (herbs at wideopenwest dot com)
>
>
>
> Hope this helps,
>
> 	Ross

Howdy,

I'll add one more thing... make sure to clean up and start fresh after something like this happens. You can use TeXShop's File->Trash Aux Files (Ctl-Cmd-A).

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)

```