On Feb 18, 2016, at 9:49 AM, Scott Kostyshak <skost...@lyx.org> 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

Reply via email to