Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Mar 3, 2016, at 5:34 PM, Guillaume Munch  wrote:

> Le 03/03/2016 23:48, Jerry a écrit :
>> the behavior is the same--Reconfigure
>> runs quickly without and crashing luatex, and the Python command
>> appears to be running very long
>> 
> 
> I am not sure I understand.
> 
What I was trying to say is that LyX 2.1 behaves the same as 2.2. 2.1 and 2.2 
originally had the same path which I posted earlier and which had some (for my 
system) nonsensical stuff at the beginning. You inquired about whether I had 
changed the path for 2.1, which I had not. So I tested 2.1 with the original 
path (I couldn't find anywhere that I had tested 2.1 with respect to this 
problem). 2.1 behaved the same as 2.2 when it had the original path. Then I 
shortened the path for 2.1 just as I had for 2.2. Then I re-tested 2.1 and with 
the shortened path it behaves the same as 2.2 when its path was shortened. The 
testing for both 2.1 and 2.2 involved running Reconfigure and also running each 
version's Python script in a terminal.

I hope that is more clear.

Jerry

Re: New versions of LyX always hang multiple times. OS X

[Guillaume Munch]

Le 03/03/2016 23:48, Jerry a écrit :

the behavior is the same--Reconfigure
runs quickly without and crashing luatex, and the Python command
appears to be running very long



I am not sure I understand.

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 28, 2016, at 12:36 PM, Guillaume Munch  wrote:

> 
> Le 27/02/2016 03:44, Jerry a écrit :
>> If I remove
>> /Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin:
>> 
>> from the front of the PATH prefix and run Reconfigure, it runs in
>> 15-20 seconds. The first time I saw a luatex instance in Activity
>> Monitor but on subsequent runs it did not appear--I suppose it's
>> possible that it ran so quickly that Activity Monitor did not have a
>> chance to show it.
>> 
>> This of course has no effect on running
>> 
>> python -tt "/Applications/Words/LyXOuterFolder/LyX
>> 2.2.0beta2/LyX.app/Contents/Resources/configure.py"
>> --with-version-suffix=-2.2
>> --binary-dir="/Applications/Words/LyXOuterFolder/LyX
>> 2.2.0beta2/LyX.app/Contents/MacOS/"
>> 
>> from a terminal session which still stays on +Indexing TeX files...
>> for about 34 minutes.
>> 
> 
Sorry for the late reply. I was sick for a few days.

> Have you changed the value of PATH under both lyx 2.1 and 2.2 ?

No, only 2.2. 2.1 has the same path as 2.2 before I changed it.

The behavior seems the same under 2.1 as 2.2. I shortened the path in 2.1 as I 
described for 2.2 and the behavior is the same--Reconfigure runs quickly 
without and crashing luatex, and the Python command

python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.1.4/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.1 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.1.4/LyX.app/Contents/MacOS/"

appears to be running very long, paused on "+Indexing TeX files...". (It is 
running as I type this.)

Jerry
> 
> I still do not understand why the above makes the two issues seem
> unrelated whereas in your description below I get the impression that
> closing the luatex processes makes you skip the 34-minute waiting time.
> 
> The luatex process starts almost as soon as I hit Reconfigure.
> I Quit it (force quit not required) using Activity Monitor.
> LyX is unresponsive for about a minute, then the message
> 
> The system has been reconfigured. You need to restart LyX to
> make use of any updated document class specifications.
> 
> appears. At that point, LyX seems to operate normally. Also it
> operates normally after quitting and relaunching.
> 

Re: New versions of LyX always hang multiple times. OS X

[Guillaume Munch]

Le 27/02/2016 03:44, Jerry a écrit :

If I remove
/Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin:

 from the front of the PATH prefix and run Reconfigure, it runs in
15-20 seconds. The first time I saw a luatex instance in Activity
Monitor but on subsequent runs it did not appear--I suppose it's
possible that it ran so quickly that Activity Monitor did not have a
 chance to show it.

This of course has no effect on running

python -tt "/Applications/Words/LyXOuterFolder/LyX
2.2.0beta2/LyX.app/Contents/Resources/configure.py"
--with-version-suffix=-2.2
--binary-dir="/Applications/Words/LyXOuterFolder/LyX
2.2.0beta2/LyX.app/Contents/MacOS/"

from a terminal session which still stays on +Indexing TeX files...
for about 34 minutes.



Have you changed the value of PATH under both lyx 2.1 and 2.2 ?

I still do not understand why the above makes the two issues seem
unrelated whereas in your description below I get the impression that
closing the luatex processes makes you skip the 34-minute waiting time.


The luatex process starts almost as soon as I hit Reconfigure.
 I Quit it (force quit not required) using Activity Monitor.
LyX is unresponsive for about a minute, then the message

The system has been reconfigured. You need to restart LyX to
make use of any updated document class specifications.

appears. At that point, LyX seems to operate normally. Also it
 operates normally after quitting and relaunching.

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 26, 2016, at 8:54 AM, Stephan Witt  wrote:

> 
>> Am 26.02.2016 um 16:41 schrieb Guillaume Munch :
>> 
>> Le 26/02/2016 10:08, Jerry a écrit :
>>> I don't know if you could infer that from my previous comments, but
>>> more or less what happens.
>> 
>> I could infer, more or less :)
>> 
>>> The luatex process starts almost as soon
>>> as I hit Reconfigure. I Quit it (force quit not required) using
>>> Activity Monitor. LyX is unresponsive for about a minute, then the
>>> message
>>> 
>>> The system has been reconfigured. You need to restart LyX to make use
>>> of any updated document class specifications.
>>> 
>>> appears. At that point, LyX seems to operate normally. Also it
>>> operates normally after quitting and relaunching.
>> 
>> This makes me think that we experienced the same issue. I would suggest to 
>> make sure that LyX does not call inadvertently the wrong luatex binary from 
>> your older texlive 2013 installation.
> 
> To achieve this please verify the PATH settings in LyX preferences. 
> They don’t have to match the PATH settings in Terminal. But this
> entry defines the PATH environment for external system commands.
> 
> Stephan

The PATH prefix in Preferences is

/Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin:/opt/local/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/usr/sbin:/sbin

also
$ echo $PATH
/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/texbin:/usr/local/bin:/usr/local/sbin:/Applications:/usr/local/ada/bin

Parsing the PATH prefix from Preferences a little...

On my system, I have a /Library/TeX/ *but there is no texbin in it*. However, 
it does contain this:
/Library/TeX/.scripts
/Library/TeX/Distributions
/Library/TeX/Documentation
/Library/TeX/Local -> symlink to /usr/local/texlive/texmf-local
/Library/TeX/Root ->  symlink to /usr/local/texlive/2013 which does contain a 
bin directory

I have a /usr/texbin which is a symlink to 
/usr/local/texlive/2013/bin/x86_64-darwin

I have no /sw/

I have no /opt/local/teTeX/

I have stuff in the remaining paths on this list.

If I remove 
/Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin: from the 
front of the PATH prefix and run Reconfigure, it runs in 15-20 seconds. The 
first time I saw a luatex instance in Activity Monitor but on subsequent runs 
it did not appear--I suppose it's possible that it ran so quickly that Activity 
Monitor did not have a chance to show it.

This of course has no effect on running 

python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"

from a terminal session which still stays on +Indexing TeX files... for about 
34 minutes.

Jerry

> 
>> If you're sure it is running the most recent version, then you could try to 
>> temporarily remove non-essential fonts and see if it gets quicker. (I do not 
>> know how to safely do this on your OS.)
> 

Re: New versions of LyX always hang multiple times. OS X

[Jean-Marc Lasgouttes]

Le 26/02/16 23:34, Richard Heck a écrit :

The backtrace suggests that it is taking a very long time just to
collect directory info. If one had a really, really big TeX
installation, could that cause this kind of problem? (That's a question
for JMarc, Jerry, not for you.)


I do not know... Could it be a recursive file system (with bad symbolic 
links)?


JMarc

Re: New versions of LyX always hang multiple times. OS X

[Richard Heck]

On 02/26/2016 05:30 PM, Jerry wrote:
> On Feb 26, 2016, at 3:27 AM, Jean-Marc Lasgouttes  wrote:
>
>> Le 26/02/2016 11:09, Jerry a écrit :
>>> On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes  
>>> wrote:
>>>
 Le 25/02/2016 10:01, Jerry a écrit :
> When I ran the Python command in a terminal, it proceeded quickly to 
> "+Indexing TeX files..." and stayed there for about 34 minutes and 
> everything else took no more than about a minute--just as before 
> installing texlive-fonts-recommended.
 Does this mean that running "python scripts/TeXFiles.py" is the command 
 that is slow?

 JMarc
>>> I don't know.
>> Could you try to run it like you ran by hand configure.py? To be frank I'd 
>> be suprised to find out that the is the culprit, but the message "+Indexing 
>> TeX files... " would point to that, unless I am mistaken.
> Sorry for my lazy answer but I sort of didn't understand it. Running 
> TeXFiles.py resulted in about 8-9 minutes spent in each of "Indexing files of 
> type cls|sty|bst|bib". Processor usage by Python was low at around 4%. The 
> rest of the remaining running time was negligible by comparison.

The backtrace suggests that it is taking a very long time just to
collect directory info. If one had a really, really big TeX
installation, could that cause this kind of problem? (That's a question
for JMarc, Jerry, not for you.)

Richard

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 26, 2016, at 3:27 AM, Jean-Marc Lasgouttes  wrote:

> Le 26/02/2016 11:09, Jerry a écrit :
>> 
>> On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes  wrote:
>> 
>>> Le 25/02/2016 10:01, Jerry a écrit :
 When I ran the Python command in a terminal, it proceeded quickly to 
 "+Indexing TeX files..." and stayed there for about 34 minutes and 
 everything else took no more than about a minute--just as before 
 installing texlive-fonts-recommended.
>>> 
>>> Does this mean that running "python scripts/TeXFiles.py" is the command 
>>> that is slow?
>>> 
>>> JMarc
>> 
>> I don't know.
> 
> Could you try to run it like you ran by hand configure.py? To be frank I'd be 
> suprised to find out that the is the culprit, but the message "+Indexing TeX 
> files... " would point to that, unless I am mistaken.

Sorry for my lazy answer but I sort of didn't understand it. Running 
TeXFiles.py resulted in about 8-9 minutes spent in each of "Indexing files of 
type cls|sty|bst|bib". Processor usage by Python was low at around 4%. The rest 
of the remaining running time was negligible by comparison.
> 
> Also, there is a question you may already have answered. What happens if you 
> interrupt the running confogure.py with Ctrl+C? Does python give you a 
> backtrace showing where it is in the configure.py script?

I ran 

python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"

and hit Ctrl-C while "+Indexing TeX files..." was displayed. This gave the 
following backtrace:

+Indexing TeX files... 
^CTraceback (most recent call last):
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py", line 1612, in 
Traceback (most recent call last):
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/scripts/TeXFiles.py", line 107, in 

for root,path,files in os.walk(dir):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 294, in walk
for x in walk(new_path, topdown, onerror, followlinks):
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", 
line 276, in walk
names = listdir(top)
KeyboardInterrupt
rescanTeXFiles()
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py", line 1525, in 
rescanTeXFiles
tfp = cmdOutput("python -tt " + '"' + os.path.join(srcdir, 'scripts', 
'TeXFiles.py') + '"')
  File "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py", line 76, in cmdOutput
output = pipe.stdout.read()
KeyboardInterrupt

Jerry

> JMarc
> 

Re: New versions of LyX always hang multiple times. OS X

[Stephan Witt]

> Am 26.02.2016 um 16:41 schrieb Guillaume Munch :
> 
> Le 26/02/2016 10:08, Jerry a écrit :
>> I don't know if you could infer that from my previous comments, but
>> more or less what happens.
> 
> I could infer, more or less :)
> 
>> The luatex process starts almost as soon
>> as I hit Reconfigure. I Quit it (force quit not required) using
>> Activity Monitor. LyX is unresponsive for about a minute, then the
>> message
>> 
>> The system has been reconfigured. You need to restart LyX to make use
>> of any updated document class specifications.
>> 
>> appears. At that point, LyX seems to operate normally. Also it
>> operates normally after quitting and relaunching.
> 
> This makes me think that we experienced the same issue. I would suggest to 
> make sure that LyX does not call inadvertently the wrong luatex binary from 
> your older texlive 2013 installation.

To achieve this please verify the PATH settings in LyX preferences. 
They don’t have to match the PATH settings in Terminal. But this
entry defines the PATH environment for external system commands.

Stephan

> If you're sure it is running the most recent version, then you could try to 
> temporarily remove non-essential fonts and see if it gets quicker. (I do not 
> know how to safely do this on your OS.)

Re: New versions of LyX always hang multiple times. OS X

[Guillaume Munch]

Le 26/02/2016 10:08, Jerry a écrit :

I don't know if you could infer that from my previous comments, but
more or less what happens.


I could infer, more or less :)


The luatex process starts almost as soon
as I hit Reconfigure. I Quit it (force quit not required) using
Activity Monitor. LyX is unresponsive for about a minute, then the
message

The system has been reconfigured. You need to restart LyX to make use
of any updated document class specifications.

appears. At that point, LyX seems to operate normally. Also it
operates normally after quitting and relaunching.


This makes me think that we experienced the same issue. I would suggest 
to make sure that LyX does not call inadvertently the wrong luatex 
binary from your older texlive 2013 installation. If you're sure it is 
running the most recent version, then you could try to temporarily 
remove non-essential fonts and see if it gets quicker. (I do not know 
how to safely do this on your OS.)

Re: New versions of LyX always hang multiple times. OS X

[José Matos]

On Friday, February 26, 2016 11:27:25 AM Jean-Marc Lasgouttes wrote:
> Also, there is a question you may already have answered. What happens if 
> you interrupt the running confogure.py with Ctrl+C? Does python give you 
> a backtrace showing where it is in the configure.py script?
> 
> JMarc

It should. :-)

The last line will be the exception KeyboardInterrupt and it will output the 
line where it stopped together with the backtrace of functions that got you in 
that line.

-- 
José Abílio

Re: New versions of LyX always hang multiple times. OS X

[Jean-Marc Lasgouttes]

Le 26/02/2016 11:09, Jerry a écrit :


On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes  wrote:


Le 25/02/2016 10:01, Jerry a écrit :

When I ran the Python command in a terminal, it proceeded quickly to "+Indexing TeX 
files..." and stayed there for about 34 minutes and everything else took no more 
than about a minute--just as before installing texlive-fonts-recommended.


Does this mean that running "python scripts/TeXFiles.py" is the command that is 
slow?

JMarc


I don't know.


Could you try to run it like you ran by hand configure.py? To be frank 
I'd be suprised to find out that the is the culprit, but the message 
"+Indexing TeX files... " would point to that, unless I am mistaken.


Also, there is a question you may already have answered. What happens if 
you interrupt the running confogure.py with Ctrl+C? Does python give you 
a backtrace showing where it is in the configure.py script?


JMarc

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes  wrote:

> Le 25/02/2016 10:01, Jerry a écrit :
>> When I ran the Python command in a terminal, it proceeded quickly to 
>> "+Indexing TeX files..." and stayed there for about 34 minutes and 
>> everything else took no more than about a minute--just as before installing 
>> texlive-fonts-recommended.
> 
> Does this mean that running "python scripts/TeXFiles.py" is the command that 
> is slow?
> 
> JMarc

I don't know.
Jerry

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 25, 2016, at 9:15 AM, Guillaume Munch  wrote:

> Le 25/02/2016 00:54, Jerry a écrit :
>> On Feb 24, 2016, at 6:49 AM, Guillaume Munch  wrote:
>> 
>>> I may have had a similar issue involving LuaTeX taking huge amounts
>>> of time to configure, at some point, with LyX 2.1 and TeXLive
>>> 2012/2013. It got solved by upgrading TeXLive. Jerry, do you have
>>> lots of fonts installed?
>> 
>> I'm not sure what you mean. If I take your question literally, the
>> answer is, it seems like everything I do on my computer results in
>> more fonts being installed, so I would say "yes," approximately 10^9.
>> I can be more precise if you like. OK--according to Font Book, there
>> are about 450 families and most have several fonts in each family.
>> 
> 
> This has been a factor for me in the past, though it's been a while ago,
> and I never really investigated the problem. When I had this problem I
> would simply force-close the luatex processes, then lyx would
> immediately continue as expected. If I infer correctly from your other
> messages, if you only force-close the luatex processes and not lyx then
> it continues normally?
> 
I don't know if you could infer that from my previous comments, but more or 
less what happens. The luatex process starts almost as soon as I hit 
Reconfigure. I Quit it (force quit not required) using Activity Monitor. LyX is 
unresponsive for about a minute, then the message 

The system has been reconfigured.
You need to restart LyX to make use of any
updated document class specifications.

appears. At that point, LyX seems to operate normally. Also it operates 
normally after quitting and relaunching.

Jerry

Re: New versions of LyX always hang multiple times. OS X

[Guillaume Munch]

Le 25/02/2016 00:54, Jerry a écrit :

On Feb 24, 2016, at 6:49 AM, Guillaume Munch  wrote:


I may have had a similar issue involving LuaTeX taking huge amounts
of time to configure, at some point, with LyX 2.1 and TeXLive
2012/2013. It got solved by upgrading TeXLive. Jerry, do you have
lots of fonts installed?


I'm not sure what you mean. If I take your question literally, the
answer is, it seems like everything I do on my computer results in
more fonts being installed, so I would say "yes," approximately 10^9.
I can be more precise if you like. OK--according to Font Book, there
are about 450 families and most have several fonts in each family.



This has been a factor for me in the past, though it's been a while ago,
and I never really investigated the problem. When I had this problem I
would simply force-close the luatex processes, then lyx would
immediately continue as expected. If I infer correctly from your other
messages, if you only force-close the luatex processes and not lyx then
it continues normally?

Re: New versions of LyX always hang multiple times. OS X

[Jean-Marc Lasgouttes]

Le 25/02/2016 10:01, Jerry a écrit :

When I ran the Python command in a terminal, it proceeded quickly to "+Indexing TeX 
files..." and stayed there for about 34 minutes and everything else took no more 
than about a minute--just as before installing texlive-fonts-recommended.


Does this mean that running "python scripts/TeXFiles.py" is the command 
that is slow?


JMarc

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 5:48 PM, Jerry  wrote:

> 
> On Feb 24, 2016, at 3:04 AM, Jean-Marc Lasgouttes  wrote:
> 
>> Le 24/02/2016 10:06, Jerry a écrit :
>>> I have two TeX installations. One I installed from the TUG (I think that's 
>>> what it's called) binary installer, probably TeXlive-2013, and the other as 
>>> part of MacPorts, macports.org; this -> "texlive-bin @2015_8+x11 (active)" 
>>> I think is relevant information for the active version from MacPorts. LyX 
>>> is seeing the MacPorts version since all of MacPorts is in /opt/local. The 
>>> TUG version from 2013 is at /usr/local/texlive/2013. I think that is 
>>> probably the whole wad since it is 3.4 GB. I have been thinking about 
>>> deleting it and relying on the well-maintained MacPorts version.
>> 
>> Do you have the package texlive-fonts-recommended installed?
> 
> I'm not sure how to tell, so I did the macports command, port...
> $ port installed texlive-fonts-recommended
> None of the specified ports are installed.
> 
> so I would say, "no". I also searched my system for 
> "texlive-fonts-recommended" and turned up only 
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/tex/texlive-fonts-recommended
> which is a portfile which is not a "yes."
> 
> However, I suspect that texlive might install fonts in the places where OS X 
> normally expects to find fonts and not in /opt/local where the rest of 
> MacPorts lives--I have a question to the macports list about that.
> 
> FWIW, the OS X font manager indicates a number of entries for Latin Modern 
> and TeX Gyre. When I put T1 into the manager's filter field, four Latin 
> Modern families appear in the list. These _might_ have been installed by my 
> other TeXLive installation from 2013 which is in /usr/something. Of course 
> the basic Postscript fonts are also installed.
> 
>> 
>> Note that we should probably not require the ec fonts to be installed. This 
>> is very old code that I wrote at the time where these fonts were something 
>> modern. It seems that it was in LyX 0.11.17, which means that it was written 
>> almost 20 years ago :)
>> 
>> I would propose to remove this code and set the document encoding to T1 by 
>> default. This whole font encoding thing has to be rethought, but I am not 
>> competent in this respect.
>> 
>> JMarc
>> 
I checked with the list at MacPorts and found that the fonts are installed in 
the MacPorts directory, not the usual OS X font locations. So I installed 
texlive-fonts-recommended and ran Reconfigure. The running time was similar, 
luatex crashed as before, I got the dialog about the Python script not 
completing, I let it run, and instead of reporting immediately that the system 
was reconfigured and I had to re-start LyX, it took maybe 30 seconds before 
that happened.

When I ran the Python command in a terminal, it proceeded quickly to "+Indexing 
TeX files..." and stayed there for about 34 minutes and everything else took no 
more than about a minute--just as before installing texlive-fonts-recommended.

I've again attached the Python output.

Jerry

Last login: Thu Feb 25 01:21:42 on ttys002
Hello, Jerry. Your profile is at ~/.profile.
MBPro:~ jerrybauck$ python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"
checking for a Latex2e program...
+checking for "latex"...  yes
checking for a DVI postprocessing program...
+checking for "pplatex"...  no
checking for pLaTeX, the Japanese LaTeX...
+checking for "platex"...  yes
checking for a java interpreter...
+checking for "java"...  yes
checking for a perl interpreter...
+checking for "perl"...  yes
checking for a Tgif viewer and editor...
+checking for "tgif"...  no
checking for a FIG viewer and editor...
+checking for "xfig"...  no
+checking for "jfig3-itext.jar"...  no
+checking for "jfig3.jar"...  no
checking for a Dia viewer and editor...
+checking for "dia"...  no
checking for an OpenDocument drawing viewer and editor...
+checking for "libreoffice"...  no
+checking for "lodraw"...  no
+checking for "ooffice"...  no
+checking for "oodraw"...  no
+checking for "soffice"...  no
checking for a Grace viewer and editor...
+checking for "xmgrace"...  no
checking for a FEN viewer and editor...
+checking for "xboard"...  no
checking for a SVG viewer and editor...
+checking for "inkscape"...  no
checking for a raster image viewer...
+checking for "xv"...  no
+checking for "kview"...  no
+checking for "gimp-remote"...  no
+checking for "gimp"...  no
checking for a raster image editor...
+checking for "gimp-remote"...  no
+checking for "gimp"...  no
checking for a text editor...
+checking for "xemacs"...  no
+checking for "gvim"...  no
+checking for "kedit"...  no
+checking for "kwrite"...  no
+checking for "kate"...  no
+checking for "nedit"...  no
+checking for "gedit"...  

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 6:49 AM, Guillaume Munch  wrote:

> I may have had a similar issue involving LuaTeX taking huge amounts of
> time to configure, at some point, with LyX 2.1.3 and TeXLive 2012/2013.
> It got solved by upgrading TeXLive. Jerry, do you have lots of fonts
> installed?

I'm not sure what you mean. If I take your question literally, the answer is, 
it seems like everything I do on my computer results in more fonts being 
installed, so I would say "yes," approximately 10^9. I can be more precise if 
you like. OK--according to Font Book, there are about 450 families and most 
have several fonts in each family.

Jerry

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 2:32 AM, Jean-Marc Lasgouttes  wrote:

> Le 24/02/2016 05:18, Jerry a écrit :
>> +checking for default encoding (this may take a long time)
>> 
>> kpathsea: Running mktextfm ecrm1000
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source 
>> abbreviation  for ecrm1000.
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
>> mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
>> input ecrm1000
>> This is METAFONT, Version 2.7182818 (TeX Live 2015/MacPorts 2015_8) 
>> (preloaded base=mf)
> 
> It looks like your installation is missing some LaTeX fonts. I see you have 
> texlive 2015, but could you give details on how you did install it?

It is installed by the package manager MacPorts, macports.org. As I understand 
it, MacPorts is a port of the BSD ports package manager. It is mostly 
well-maintained and Apple pays a full-time person to help the cause. I didn't 
explicitly install it but I'm sure it was installed as a dependency of some 
other package but not LyX as I've never used MacPorts to install LyX. FWIW, the 
first two items on my PATH variable are /opt/local/bin:/opt/local/sbin.
> 
> One possibility is that you have a wrong luatex binary somewhere on your 
> path: 
> http://tex.stackexchange.com/questions/116332/latex-compilation-of-simple-document-fails
> 
> What does the command "which luatex" return?

/opt/local/bin/luatex
As noted before, /opt/local/ is where all of MacPorts is installed, and only 
MacPorts.
Also:

$ luatex
This is LuaTeX, Version beta-0.80.0 (TeX Live 2015/MacPorts 2015_8) (rev 5238) 
 restricted \write18 enabled.

> 
> JMarc

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 24, 2016, at 3:04 AM, Jean-Marc Lasgouttes  wrote:

> Le 24/02/2016 10:06, Jerry a écrit :
>> I have two TeX installations. One I installed from the TUG (I think that's 
>> what it's called) binary installer, probably TeXlive-2013, and the other as 
>> part of MacPorts, macports.org; this -> "texlive-bin @2015_8+x11 (active)" I 
>> think is relevant information for the active version from MacPorts. LyX is 
>> seeing the MacPorts version since all of MacPorts is in /opt/local. The TUG 
>> version from 2013 is at /usr/local/texlive/2013. I think that is probably 
>> the whole wad since it is 3.4 GB. I have been thinking about deleting it and 
>> relying on the well-maintained MacPorts version.
> 
> Do you have the package texlive-fonts-recommended installed?

I'm not sure how to tell, so I did the macports command, port...
$ port installed texlive-fonts-recommended
None of the specified ports are installed.

so I would say, "no". I also searched my system for "texlive-fonts-recommended" 
and turned up only 
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/tex/texlive-fonts-recommended
which is a portfile which is not a "yes."

However, I suspect that texlive might install fonts in the places where OS X 
normally expects to find fonts and not in /opt/local where the rest of MacPorts 
lives--I have a question to the macports list about that.

FWIW, the OS X font manager indicates a number of entries for Latin Modern and 
TeX Gyre. When I put T1 into the manager's filter field, four Latin Modern 
families appear in the list. These _might_ have been installed by my other 
TeXLive installation from 2013 which is in /usr/something. Of course the basic 
Postscript fonts are also installed.

> 
> Note that we should probably not require the ec fonts to be installed. This 
> is very old code that I wrote at the time where these fonts were something 
> modern. It seems that it was in LyX 0.11.17, which means that it was written 
> almost 20 years ago :)
> 
> I would propose to remove this code and set the document encoding to T1 by 
> default. This whole font encoding thing has to be rethought, but I am not 
> competent in this respect.
> 
> JMarc
> 
> 

Re: New versions of LyX always hang multiple times. OS X

[Guillaume Munch]

I may have had a similar issue involving LuaTeX taking huge amounts of
time to configure, at some point, with LyX 2.1.3 and TeXLive 2012/2013.
It got solved by upgrading TeXLive. Jerry, do you have lots of fonts
installed?



Le 24/02/2016 09:06, Jerry a écrit :


On Feb 23, 2016, at 9:46 PM, Scott Kostyshak  wrote:


On Tue, Feb 23, 2016 at 09:18:50PM -0700, Jerry wrote:


On Feb 23, 2016, at 3:28 PM, Scott Kostyshak  wrote:



Jerry does this happen even when Flexiglass is not running?


Yes. The behavior is the same, which is, using a non-new LyX but running Reconfigure, one 
instance of luatex hitting 200-250 MB (it can vary 10s of MB between Activity Monitor 
updates, which is about 3 seconds--Activity Monitor is I believe eye candy over tops) and 
roughly 20-100% of a single CPU. That luatex crashes in 4-5 minutes. The message about 
the Python command not finishing is displayed. Clicking "let it run" causes a 
message displayed that the system has been reconfigured and to restart LyX. LyX does not 
crash.

I'll try to remember to quit Flexiglass when doing LyX testing but I probably 
use it a hundred+ times a day.


I imagine it is hard. Actually the useful thing is to know whether you
can reproduce bugs that you find when Flexiglass is not running. So you
do not always have to remember to turn it off, but maybe it is hard to
remember to do it even in these cases.


Can you run that python command manually in a terminal?

Yes

Can you
reproduce the freeze when you do this?

No. The command ran for 35 minutes with almost of it with the line "+Indexing TeX 
files..." displayed.


This is important information. 35 minutes is not normal. For me it takes 9 
seconds (although I would not be surprised if it takes up to a couple of 
minutes on some computers).


There were two Python instances during this time, one possibly spawned by the 
other. It (they) appear(s) to have finished normally. In my home directory the 
following files and directories--all empty--were created. I'm going to trash 
them.


I forgot to specify that normally this command would be run from your
LyX user directory (which you can find the location of in Help > About).


+Indexing TeX files...


So this is where it pauses for a long time? How many minutes out of the
35?


Almost all--I'd guess 33-34.



+checking for default encoding (this may take a long time)


This is the only place where we say that it might take a long time. Does
the script pause here for a while?


I didn't notice it stopping for very long at all here or otherwise except as 
noted. I kept part of the terminal window visible as I did other things on my 
computer so I might have missed some details, but my strong impression is that 
everything flew by except the Indexing TeX files line. I would be happy to run 
it again if that would be helpful.

Jerry



kpathsea: Running mktextfm ecrm1000
/opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source 
abbreviation  for ecrm1000.
/opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
input ecrm1000
This is METAFONT, Version 2.7182818 (TeX Live 2015/MacPorts 2015_8) (preloaded 
base=mf)


kpathsea: Running mktexmf ecrm1000
! I can't find file `ecrm1000'.
<*> ...ljfour; mag:=1; nonstopmode; input ecrm1000

Please type another input file name
! Emergency stop.
<*> ...ljfour; mag:=1; nonstopmode; input ecrm1000

Transcript written on mfput.log.
grep: ecrm1000.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input 
ecrm1000' failed to make ecrm1000.tfm.
kpathsea: Appending font creation commands to missfont.log.


This doesn't look normal. I'm not sure if it's LyX's fault or your TeX
installation. Whatever it is, LyX should at least exit with error here,
no?


I have two TeX installations. One I installed from the TUG (I think that's what it's called) 
binary installer, probably TeXlive-2013, and the other as part of MacPorts, macports.org; 
this -> "texlive-bin @2015_8+x11 (active)" I think is relevant information for 
the active version from MacPorts. LyX is seeing the MacPorts version since all of MacPorts 
is in /opt/local. The TUG version from 2013 is at /usr/local/texlive/2013. I think that is 
probably the whole wad since it is 3.4 GB. I have been thinking about deleting it and 
relying on the well-maintained MacPorts version.

Jerry



Python terminal output.txt


To make sure I understand correctly, you experienced a similar problem
with LyX 2.1.x except that LyX did not crash. What is new in beta2 is
that LyX crashes. Did I get that right?

I can't remember if LyX has actually ever crashed in this respect--it rather 
seems to become unresponsive while the one or two luatex are running, 2.1.x and 
2.2.x. I seem to recall that when first running a new version I might have had 
to force-quit LyX after the two luatex instances either 

Re: New versions of LyX always hang multiple times. OS X

[Jean-Marc Lasgouttes]

Le 24/02/2016 10:06, Jerry a écrit :

I have two TeX installations. One I installed from the TUG (I think that's what it's called) 
binary installer, probably TeXlive-2013, and the other as part of MacPorts, macports.org; 
this -> "texlive-bin @2015_8+x11 (active)" I think is relevant information for 
the active version from MacPorts. LyX is seeing the MacPorts version since all of MacPorts 
is in /opt/local. The TUG version from 2013 is at /usr/local/texlive/2013. I think that is 
probably the whole wad since it is 3.4 GB. I have been thinking about deleting it and 
relying on the well-maintained MacPorts version.


Do you have the package texlive-fonts-recommended installed?

Note that we should probably not require the ec fonts to be installed. 
This is very old code that I wrote at the time where these fonts were 
something modern. It seems that it was in LyX 0.11.17, which means that 
it was written almost 20 years ago :)


I would propose to remove this code and set the document encoding to T1 
by default. This whole font encoding thing has to be rethought, but I am 
not competent in this respect.


JMarc

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 23, 2016, at 9:46 PM, Scott Kostyshak  wrote:

> On Tue, Feb 23, 2016 at 09:18:50PM -0700, Jerry wrote:
>> 
>> On Feb 23, 2016, at 3:28 PM, Scott Kostyshak  wrote:
> 
>>> Jerry does this happen even when Flexiglass is not running?
>> 
>> Yes. The behavior is the same, which is, using a non-new LyX but running 
>> Reconfigure, one instance of luatex hitting 200-250 MB (it can vary 10s of 
>> MB between Activity Monitor updates, which is about 3 seconds--Activity 
>> Monitor is I believe eye candy over tops) and roughly 20-100% of a single 
>> CPU. That luatex crashes in 4-5 minutes. The message about the Python 
>> command not finishing is displayed. Clicking "let it run" causes a message 
>> displayed that the system has been reconfigured and to restart LyX. LyX does 
>> not crash.
>> 
>> I'll try to remember to quit Flexiglass when doing LyX testing but I 
>> probably use it a hundred+ times a day.
> 
> I imagine it is hard. Actually the useful thing is to know whether you
> can reproduce bugs that you find when Flexiglass is not running. So you
> do not always have to remember to turn it off, but maybe it is hard to
> remember to do it even in these cases.
> 
>>> Can you run that python command manually in a terminal?
>> Yes
>>> Can you
>>> reproduce the freeze when you do this?
>> No. The command ran for 35 minutes with almost of it with the line 
>> "+Indexing TeX files..." displayed.
> 
> This is important information. 35 minutes is not normal. For me it takes 9 
> seconds (although I would not be surprised if it takes up to a couple of 
> minutes on some computers).
> 
>> There were two Python instances during this time, one possibly spawned by 
>> the other. It (they) appear(s) to have finished normally. In my home 
>> directory the following files and directories--all empty--were created. I'm 
>> going to trash them.
> 
> I forgot to specify that normally this command would be run from your
> LyX user directory (which you can find the location of in Help > About).
> 
>> +Indexing TeX files... 
> 
> So this is where it pauses for a long time? How many minutes out of the
> 35?

Almost all--I'd guess 33-34.
> 
>> +checking for default encoding (this may take a long time)
> 
> This is the only place where we say that it might take a long time. Does
> the script pause here for a while?

I didn't notice it stopping for very long at all here or otherwise except as 
noted. I kept part of the terminal window visible as I did other things on my 
computer so I might have missed some details, but my strong impression is that 
everything flew by except the Indexing TeX files line. I would be happy to run 
it again if that would be helpful.

Jerry
> 
>> kpathsea: Running mktextfm ecrm1000
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source 
>> abbreviation  for ecrm1000.
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
>> mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
>> input ecrm1000
>> This is METAFONT, Version 2.7182818 (TeX Live 2015/MacPorts 2015_8) 
>> (preloaded base=mf)
>> 
>> 
>> kpathsea: Running mktexmf ecrm1000
>> ! I can't find file `ecrm1000'.
>> <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000
>> 
>> Please type another input file name
>> ! Emergency stop.
>> <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000
>> 
>> Transcript written on mfput.log.
>> grep: ecrm1000.log: No such file or directory
>> mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input 
>> ecrm1000' failed to make ecrm1000.tfm.
>> kpathsea: Appending font creation commands to missfont.log.
> 
> This doesn't look normal. I'm not sure if it's LyX's fault or your TeX
> installation. Whatever it is, LyX should at least exit with error here,
> no?

I have two TeX installations. One I installed from the TUG (I think that's what 
it's called) binary installer, probably TeXlive-2013, and the other as part of 
MacPorts, macports.org; this -> "texlive-bin @2015_8+x11 (active)" I think is 
relevant information for the active version from MacPorts. LyX is seeing the 
MacPorts version since all of MacPorts is in /opt/local. The TUG version from 
2013 is at /usr/local/texlive/2013. I think that is probably the whole wad 
since it is 3.4 GB. I have been thinking about deleting it and relying on the 
well-maintained MacPorts version.

Jerry
> 
>> Python terminal output.txt
>>> 
>>> To make sure I understand correctly, you experienced a similar problem
>>> with LyX 2.1.x except that LyX did not crash. What is new in beta2 is
>>> that LyX crashes. Did I get that right?
>> I can't remember if LyX has actually ever crashed in this respect--it rather 
>> seems to become unresponsive while the one or two luatex are running, 2.1.x 
>> and 2.2.x. I seem to recall that when first running a new version I might 
>> have had to force-quit LyX after the two luatex instances either crashed (at 
>> least one) or I killed them.

Re: New versions of LyX always hang multiple times. OS X

[Jean-Marc Lasgouttes]

Le 24/02/2016 05:18, Jerry a écrit :

+checking for default encoding (this may take a long time)

kpathsea: Running mktextfm ecrm1000
/opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source 
abbreviation  for ecrm1000.
/opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
input ecrm1000
This is METAFONT, Version 2.7182818 (TeX Live 2015/MacPorts 2015_8) (preloaded 
base=mf)


It looks like your installation is missing some LaTeX fonts. I see you 
have texlive 2015, but could you give details on how you did install it?


One possibility is that you have a wrong luatex binary somewhere on your 
path: 
http://tex.stackexchange.com/questions/116332/latex-compilation-of-simple-document-fails


What does the command "which luatex" return?

JMarc

Re: New versions of LyX always hang multiple times. OS X

[Scott Kostyshak]

On Tue, Feb 23, 2016 at 09:18:50PM -0700, Jerry wrote:
> 
> On Feb 23, 2016, at 3:28 PM, Scott Kostyshak  wrote:

> > Jerry does this happen even when Flexiglass is not running?
> 
> Yes. The behavior is the same, which is, using a non-new LyX but running 
> Reconfigure, one instance of luatex hitting 200-250 MB (it can vary 10s of MB 
> between Activity Monitor updates, which is about 3 seconds--Activity Monitor 
> is I believe eye candy over tops) and roughly 20-100% of a single CPU. That 
> luatex crashes in 4-5 minutes. The message about the Python command not 
> finishing is displayed. Clicking "let it run" causes a message displayed that 
> the system has been reconfigured and to restart LyX. LyX does not crash.
> 
> I'll try to remember to quit Flexiglass when doing LyX testing but I probably 
> use it a hundred+ times a day.

I imagine it is hard. Actually the useful thing is to know whether you
can reproduce bugs that you find when Flexiglass is not running. So you
do not always have to remember to turn it off, but maybe it is hard to
remember to do it even in these cases.

> > Can you run that python command manually in a terminal?
> Yes
> > Can you
> > reproduce the freeze when you do this?
> No. The command ran for 35 minutes with almost of it with the line "+Indexing 
> TeX files..." displayed.

This is important information. 35 minutes is not normal. For me it takes 9 
seconds (although I would not be surprised if it takes up to a couple of 
minutes on some computers).

> There were two Python instances during this time, one possibly spawned by the 
> other. It (they) appear(s) to have finished normally. In my home directory 
> the following files and directories--all empty--were created. I'm going to 
> trash them.

I forgot to specify that normally this command would be run from your
LyX user directory (which you can find the location of in Help > About).

> +Indexing TeX files... 

So this is where it pauses for a long time? How many minutes out of the
35?

> +checking for default encoding (this may take a long time)

This is the only place where we say that it might take a long time. Does
the script pause here for a while?

> kpathsea: Running mktextfm ecrm1000
> /opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source 
> abbreviation  for ecrm1000.
> /opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
> mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
> input ecrm1000
> This is METAFONT, Version 2.7182818 (TeX Live 2015/MacPorts 2015_8) 
> (preloaded base=mf)
> 
> 
> kpathsea: Running mktexmf ecrm1000
> ! I can't find file `ecrm1000'.
> <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000
>   
> Please type another input file name
> ! Emergency stop.
> <*> ...ljfour; mag:=1; nonstopmode; input ecrm1000
>   
> Transcript written on mfput.log.
> grep: ecrm1000.log: No such file or directory
> mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input 
> ecrm1000' failed to make ecrm1000.tfm.
> kpathsea: Appending font creation commands to missfont.log.

This doesn't look normal. I'm not sure if it's LyX's fault or your TeX
installation. Whatever it is, LyX should at least exit with error here,
no?

>  Python terminal output.txt
> > 
> > To make sure I understand correctly, you experienced a similar problem
> > with LyX 2.1.x except that LyX did not crash. What is new in beta2 is
> > that LyX crashes. Did I get that right?
> I can't remember if LyX has actually ever crashed in this respect--it rather 
> seems to become unresponsive while the one or two luatex are running, 2.1.x 
> and 2.2.x. I seem to recall that when first running a new version I might 
> have had to force-quit LyX after the two luatex instances either crashed (at 
> least one) or I killed them.
> 
> I just also ran Reconfigure on LyX 2.1.4 which is not a new installation, 
> with the same results as 2.2.0beta, different path to the Python command 
> notwithstanding.

OK so it seems that this is not a regression. This is good to know
(although it makes finding the cause more difficult).

Scott


signature.asc
Description: PGP signature

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 23, 2016, at 3:28 PM, Scott Kostyshak  wrote:

> On Fri, Feb 19, 2016 at 08:08:27PM -0700, Jerry wrote:
>> 
>> On Feb 18, 2016, at 9:49 AM, Scott Kostyshak  wrote:
>> 
>>> On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
 *Every*time* I first launch a new version of LyX, something like this 
 happens: 
>>> 
>>> So to confirm, this is nothing new in 2.2.0 right? You remember seeing
>>> this in 2.1.x?
>>> 
 LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with 
 maybe 5 MB RAM but two luatex processes start up. Over a few minutes, they 
 ramp up so that each consumes 200+ MB and up to nearly 100% CPU usage. (I 
 have two cores.) The RAM and CPU usage vary somewhat, and take a few 
 minutes to reach those numbers. I force-quit both luatex and LyX itself. 
 Relaunch. One luatex process starts, along with LyX which is unresponsive. 
 The luatex process crashes after a few minutes. I force-quit LyX. 
 Relaunch, and then LyX runs normally.
 
 This has happened for a long time, over several dev and release versions 
 of LyX. However, this process has always terminated with LyX running 
 successfully.
 
 This just happened with 2.2.0beta2.
>>> 
>>> I'm guessing this is because of reconfigure. Can you do the following to
>>> confirm that it is because of reconfigure?
>>> 
>>> Click on LyX > Reconfigure. Does this reproduce the large RAM
>>> consumption and the 100% CPU spike?
>>> 
>>> Scott
>> 
>> Yes. Luatex ran one process, eventually hitting ~100% and ~200 MB, then 
>> crashed after about 4-5 minutes. I didn't see Python in call stack of the 
>> crash log but I did get this message in a dialog box:
>> 
>> The command
>> python -tt "/Applications/Words/LyXOuterFolder/LyX 
>> 2.2.0beta2/LyX.app/Contents/Resources/configure.py" 
>> --with-version-suffix=-2.2 
>> --binary-dir="/Applications/Words/LyXOuterFolder/LyX 
>> 2.2.0beta2/LyX.app/Contents/MacOS/"
>> has not yet completed.
>> 
>> Do you want to stop it?
>> 
>> I clicked on Continue or whatever the choice was and immediately got:
>> 
>> The system has been reconfigured.
>> You need to restart LyX to make use of any
>> updated document class specifications.
>> 
>> I quit LyX and relaunched, then ran Reconfigure again with the same result.
> 
> Jerry does this happen even when Flexiglass is not running?

Yes. The behavior is the same, which is, using a non-new LyX but running 
Reconfigure, one instance of luatex hitting 200-250 MB (it can vary 10s of MB 
between Activity Monitor updates, which is about 3 seconds--Activity Monitor is 
I believe eye candy over tops) and roughly 20-100% of a single CPU. That luatex 
crashes in 4-5 minutes. The message about the Python command not finishing is 
displayed. Clicking "let it run" causes a message displayed that the system has 
been reconfigured and to restart LyX. LyX does not crash.

I'll try to remember to quit Flexiglass when doing LyX testing but I probably 
use it a hundred+ times a day.
> 
> Can you run that python command manually in a terminal?
Yes
> Can you
> reproduce the freeze when you do this?
No. The command ran for 35 minutes with almost of it with the line "+Indexing 
TeX files..." displayed. There were two Python instances during this time, one 
possibly spawned by the other. It (they) appear(s) to have finished normally. 
In my home directory the following files and directories--all empty--were 
created. I'm going to trash them.

configure.log
lyxrc.defaults
packages.lst
textclass.lst
lyxmodules.lst
bibFiles.lst
bstFiles.lst
styFiles.lst
clsFiles.lst
bind
clipart
doc
examples
images
kbd
layouts
scripts
templates
ui

> What is the last line of output
> before the script freezes?
It doesn't freeze--see above.
> Can you copy and save the entire output from
> running that script manually?
It is attached.Last login: Tue Feb 23 03:19:16 on ttys002
MBPro:~ me$ python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"
checking for a Latex2e program...
+checking for "latex"...  yes
checking for a DVI postprocessing program...
+checking for "pplatex"...  no
checking for pLaTeX, the Japanese LaTeX...
+checking for "platex"...  yes
checking for a java interpreter...
+checking for "java"...  yes
checking for a perl interpreter...
+checking for "perl"...  yes
checking for a Tgif viewer and editor...
+checking for "tgif"...  no
checking for a FIG viewer and editor...
+checking for "xfig"...  no
+checking for "jfig3-itext.jar"...  no
+checking for "jfig3.jar"...  no
checking for a Dia viewer and editor...
+checking for "dia"...  no
checking for an OpenDocument drawing viewer and editor...
+checking for "libreoffice"...  no
+checking for "lodraw"...  no
+checking for "ooffice"...  no
+checking for "oodraw"...  no
+checking for 

Re: New versions of LyX always hang multiple times. OS X

[Scott Kostyshak]

On Fri, Feb 19, 2016 at 08:08:27PM -0700, Jerry wrote:
> 
> On Feb 18, 2016, at 9:49 AM, Scott Kostyshak  wrote:
> 
> > On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
> >> *Every*time* I first launch a new version of LyX, something like this 
> >> happens: 
> > 
> > So to confirm, this is nothing new in 2.2.0 right? You remember seeing
> > this in 2.1.x?
> > 
> >> LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with 
> >> maybe 5 MB RAM but two luatex processes start up. Over a few minutes, they 
> >> ramp up so that each consumes 200+ MB and up to nearly 100% CPU usage. (I 
> >> have two cores.) The RAM and CPU usage vary somewhat, and take a few 
> >> minutes to reach those numbers. I force-quit both luatex and LyX itself. 
> >> Relaunch. One luatex process starts, along with LyX which is unresponsive. 
> >> The luatex process crashes after a few minutes. I force-quit LyX. 
> >> Relaunch, and then LyX runs normally.
> >> 
> >> This has happened for a long time, over several dev and release versions 
> >> of LyX. However, this process has always terminated with LyX running 
> >> successfully.
> >> 
> >> This just happened with 2.2.0beta2.
> > 
> > I'm guessing this is because of reconfigure. Can you do the following to
> > confirm that it is because of reconfigure?
> > 
> > Click on LyX > Reconfigure. Does this reproduce the large RAM
> > consumption and the 100% CPU spike?
> > 
> > Scott
> 
> Yes. Luatex ran one process, eventually hitting ~100% and ~200 MB, then 
> crashed after about 4-5 minutes. I didn't see Python in call stack of the 
> crash log but I did get this message in a dialog box:
> 
>  The command
> python -tt "/Applications/Words/LyXOuterFolder/LyX 
> 2.2.0beta2/LyX.app/Contents/Resources/configure.py" 
> --with-version-suffix=-2.2 
> --binary-dir="/Applications/Words/LyXOuterFolder/LyX 
> 2.2.0beta2/LyX.app/Contents/MacOS/"
> has not yet completed.
> 
> Do you want to stop it?
> 
> I clicked on Continue or whatever the choice was and immediately got:
> 
>  The system has been reconfigured.
> You need to restart LyX to make use of any
> updated document class specifications.
> 
> I quit LyX and relaunched, then ran Reconfigure again with the same result.

Jerry does this happen even when Flexiglass is not running?

Can you run that python command manually in a terminal? Can you
reproduce the freeze when you do this? What is the last line of output
before the script freezes? Can you copy and save the entire output from
running that script manually?

To make sure I understand correctly, you experienced a similar problem
with LyX 2.1.x except that LyX did not crash. What is new in beta2 is
that LyX crashes. Did I get that right?

Thanks for your testing and help in debugging,

Scott


signature.asc
Description: PGP signature

Re: New versions of LyX always hang multiple times. OS X

[Jerry]

On Feb 18, 2016, at 9:49 AM, Scott Kostyshak  wrote:

> On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
>> *Every*time* I first launch a new version of LyX, something like this 
>> happens: 
> 
> So to confirm, this is nothing new in 2.2.0 right? You remember seeing
> this in 2.1.x?
> 
>> LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with 
>> maybe 5 MB RAM but two luatex processes start up. Over a few minutes, they 
>> ramp up so that each consumes 200+ MB and up to nearly 100% CPU usage. (I 
>> have two cores.) The RAM and CPU usage vary somewhat, and take a few minutes 
>> to reach those numbers. I force-quit both luatex and LyX itself. Relaunch. 
>> One luatex process starts, along with LyX which is unresponsive. The luatex 
>> process crashes after a few minutes. I force-quit LyX. Relaunch, and then 
>> LyX runs normally.
>> 
>> This has happened for a long time, over several dev and release versions of 
>> LyX. However, this process has always terminated with LyX running 
>> successfully.
>> 
>> This just happened with 2.2.0beta2.
> 
> I'm guessing this is because of reconfigure. Can you do the following to
> confirm that it is because of reconfigure?
> 
> Click on LyX > Reconfigure. Does this reproduce the large RAM
> consumption and the 100% CPU spike?
> 
> Scott

Yes. Luatex ran one process, eventually hitting ~100% and ~200 MB, then crashed 
after about 4-5 minutes. I didn't see Python in call stack of the crash log but 
I did get this message in a dialog box:

 The command
python -tt "/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/Resources/configure.py" --with-version-suffix=-2.2 
--binary-dir="/Applications/Words/LyXOuterFolder/LyX 
2.2.0beta2/LyX.app/Contents/MacOS/"
has not yet completed.

Do you want to stop it?

I clicked on Continue or whatever the choice was and immediately got:

 The system has been reconfigured.
You need to restart LyX to make use of any
updated document class specifications.

I quit LyX and relaunched, then ran Reconfigure again with the same result.

Jerry

Re: New versions of LyX always hang multiple times. OS X

[Scott Kostyshak]

On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
> *Every*time* I first launch a new version of LyX, something like this 
> happens: 

So to confirm, this is nothing new in 2.2.0 right? You remember seeing
this in 2.1.x?

> LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with maybe 
> 5 MB RAM but two luatex processes start up. Over a few minutes, they ramp up 
> so that each consumes 200+ MB and up to nearly 100% CPU usage. (I have two 
> cores.) The RAM and CPU usage vary somewhat, and take a few minutes to reach 
> those numbers. I force-quit both luatex and LyX itself. Relaunch. One luatex 
> process starts, along with LyX which is unresponsive. The luatex process 
> crashes after a few minutes. I force-quit LyX. Relaunch, and then LyX runs 
> normally.
> 
> This has happened for a long time, over several dev and release versions of 
> LyX. However, this process has always terminated with LyX running 
> successfully.
> 
> This just happened with 2.2.0beta2.

I'm guessing this is because of reconfigure. Can you do the following to
confirm that it is because of reconfigure?

Click on LyX > Reconfigure. Does this reproduce the large RAM
consumption and the 100% CPU spike?

Scott


signature.asc
Description: PGP signature