[OS X TeX] TeXShop crash problem

Nestor Aguilera nestoreaguilera at gmail.com
Mon Jun 22 09:24:58 EDT 2020


Hi:

It might be the case that the program solving the ode doesn't release memory after finishing and the operating system is using secondary memory (perhaps a hard disk?). 

Perhaps with a modern computer and newer macOS this doesn't happen, but I would suggest that you look in Activity Monitor how much memory is used 1) after compiling and the pdf is produced and 2) after quitting TeXShop and opening it again but before compilation. 

Best,

Nestor

===============================================

> On 22 Jun 2020, at 09:17, Herbert Schulz <herbs at wideopenwest.com> wrote:
> 
>> On Jun 21, 2020, at 4:17 PM, Nitecki, Zbigniew H. <Zbigniew.Nitecki at tufts.edu> wrote:
>> 
>> This is the second of two emails to this list concerning problems I ran into while working on a 50-page set of notes.  I managed to work around this problem, but it was difficult.  In the previous email, I gave an example of a problem with hyperlinks.  My other problem (which I will describe here) is of a different nature (as far as I can tell).
>> 
>> I should say that the notes made extensive use of the pst-ode program, that runs simulations of solutions to a system of two ordinary differential equations and which I imagine is highly memory-intensive.  This may be at the root of my problem: in any case, the compiling of a pdf from the source takes considerably more time than a paper of 50 pages normally would—time comparable to what it used to take to typeset my 500-page book.  Also, during the process of compiling, the process occasionally pauses, and only contnues (but with no error messages) if I go to the console and hit return.
>> 
>> But my problem is that once a pdf has been generated (and I am viewing it in the TeXShop preview window) almost any search function I use causes the whole thing to crash.  This (always) happens if I go to the toolbar at the top and type in a page number other than the one currently displayed and then hit return;  it (always) happens if I use the command-f search function.  Sometimes it occurs in an apparently spontaneous way.  It wasn’t happening when I started writing up the notes, only after they reached a certain length.  But since then, it was completely predictable that it would happen.  I would have to force quit TeXShop.  When I did so and returned to TeXShop, then so long as I didn’t typeset again, these functions seemed to work fine.
>> 
>> It is of course difficult to provide a mnimal example of this problem.  But if there are suggestions as to where I can look for the source of the problem, I’d love to hear it.
>> 
>> Oh, and I am running TeXShop 4.44 (which my computer tells me is the latest version) in Mojave 10.14.6 on a 2017 MacBook Pro with 3.1 GHz intel core i7 and the memory (I’m copying the hieroglyphics from “about this Mac”) reads “16 GB 2133MHz LP DDR3”.
>> 
>> 
>> Zbigniew Nitecki
>> Department of Mathematics
>> Tufts University
>> Medford, MA 02155
> 
> Howdy,
> 
> This may be a PDFKit bug rather than restricted to TeXShop. Could you see if the problem occurs if you use Adobe Reader which doesn't use PDFKit to display pdf files (Preview, Skim and most other Previewers do use PDFKit).
> 
> Good Luck,
> 
> Herb Schulz
> (herbs at wideopenwest dot com)
> 
> ----------- Please Consult the Following Before Posting -----------
> TeX FAQ: http://www.tex.ac.uk/faq
> List Reminders and Etiquette: https://sites.esm.psu.edu/~gray/tex/
> List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
>                https://email.esm.psu.edu/pipermail/macosx-tex/
> TeX on Mac OS X Website: http://mactex-wiki.tug.org/
> List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex



More information about the MacOSX-TeX mailing list