Cold start-up crash

For the last couple of mornings, since moving to the latest beta (Logos Bible Software 4.0b (4.10.4.7689)), L4Mac had ground to a halt within a couple of minutes, with the spinning disc working over time!

I happened to look using Activity Monitor and saw that L4Mac was using 1.5 Gb of real memory (not the indexer, L4Mac).

If I then force quit L4Mac and re-launched it, it would launch more quickly and settle down at bout 250Mb of real memory, which is what I would expect of a handful of bibles, commentaries and note files. The speed of L4Mac seemed then to be good for the rest of my session. The real memory use did continue to rise without my opening any new resources but I could ascribe that to caching of pages as I moved around the resources, and the extra memory use would have taken all day to become a problem.

I wonder if anybody else has noticed this? If you have a slow L4Mac, try force quit and re-launchof L4Mac (not of the Mac itself).

Archive.zip

Find more posts tagged with

Comments

Martin Folley

I have spent a little more time with this today.

I can replicate it every time.

The first time I launch L4 it will load and then keep grabbing memory until it falls over at about 1.5 Gb, all the timethe CPU% fluctuates between 80% and 200% .

A force quit is needed.

The next time I load L4 all works correctly, high CPU load until set up, then settling down at about 0.5% ... and I can exit normally.

Launch #3 ... a 1.5 Gb crash ... Force quit

Launch #4 ... OK ... normal exit

Launch #5 ... a 1.5 Gb crash ....

Launch #6 ... works Ok etc.

The pattern is clear, the problem I would not like to guess!

Something in the shutdown procedure seems to be leaving something in the system state in such a way that it will cause slow performance and an eventual crash the next time L4 is loaded.

Whatever this something is, it is bypassed when the application is 'Force Quit'.

Logos Bible Software 4.0b (4.10.4.7689)

0537.Archive.zip

Melissa Snyder

Is L4 opening to the home page or last session? If it opens to last session, does it always open to the same named layout, and does it make any difference to open to a 'blank layout'? Do you have "Use Internet" enabled or disabled?

Martin Folley

https://community.logos.com/discussion/comment/196196#Comment_196196

It always reloads to the last layout.

'Use Internet' is Yes

I used 'Close All' and then exited L4Mac (to save the state). (cmd-Q to exit)

On reload, the memory use settled quickly at about 150Mb (as opposed to 250Mb with some open resources) before starting to climb back up to the 1.5 Gb RAM use where Activity Monitor starts to lose function since L4Mac is so unresponsive.

With a fresh start and a blank layout I enabled the home page to run upon start up. This went to about 160Mb initially before it also started the inevitable hike skywards.

As a pure personal perception thing, the rate at which iL4Mac 'eats' RAM seems to be proportional to the number of resources that are opened initially.

1638.Archive.zip

Melissa Snyder

https://community.logos.com/discussion/comment/196749#Comment_196749

Thanks for trying those steps. I'll submit your logs for review to see if they provide information about the 1.5GB RAM usage.

Melissa Snyder

https://community.logos.com/discussion/comment/196749#Comment_196749

Your Logos4_Crash.txt is dated Nov 19 and Console Messages.log is from Oct 9. Would it be possible to get an updated Console Messages.log from when the memory usage ramps up? Did this recent behavior start on the 19th or on the 24th when you posted?

Martin Folley

https://community.logos.com/discussion/comment/196782#Comment_196782

The problems started with the latest Mac Beta (which ever date that was).

I do not know why the consoles message log is so old. I thought I had compiled the zip file in accordance with the forum instructions after my last post. [^o)]

I will clear the lot and try again.

Martin Folley

https://community.logos.com/discussion/comment/196796#Comment_196796

New logs ...

1. Starting whereever I left off (!), I cannot remember if my last action was Quit or force quit.

L4Mac has opened to the home page. I have left it there, switched to Activity Monitor and am watching the RAM go up. Wait until 500Mb RAM is used, I want to move on before it is too unresponsive.

Switching off 'Home page at start', quitting L4Mac (cmd-Q) and relaunching ...

2. L4Mac opens with a blank workspace, settles quickly to 150Mb RAM, and then proceeds to climb. The CPU % ranges from 30% to 150% even though there are no resources and L4Mac does not have the focus. Again, moving on once beyond 500 MB RAM use.

Loading my devotional layout, quit (cmd-Q) and re-launch.

3. L4Mac has opened to my layout. Shot up to 260Mb RAM use as everything appeared. CPU% dropped back to 40% at this point and is again fluctuating between 40% and 180%. The RAM is increasing steadily. Actually, as the RAM use goes up so does the CPU use. At 680 Mb RAM, the CPU moves between 120 and 220%.

Finally (at 1Gb RAM) ... A Force quit and then run L4Mac again ...

4. This time up to 250% CPU load, loads the resources, and CPU goes to 0.4% (idle) and the RAM usage is stable at 255.0 Mb. Five minutes later, RAM use has very slowly crept up to 302.5 Mb, but that could be my premature assumption that everything was finished by 255Mb. 10 minutes later it is still stable at 302.5 Mb

A quick play in the stable state ... very responsive indeed ... opening and closing a couple of resources, and a basic text search.

Close Normally and then re-launch

5. ... and back to the RAM eating!

Of the five application lunches, three (2,3,5) were after a clean close and resulted in RAM eating. One was after a force quit (4), and produced a very responsive system). I do not know the provenance of the other one (1) .

Hope this helps.

5810.Archive.zip

Melissa Snyder

https://community.logos.com/discussion/comment/196821#Comment_196821

New logs ...

Hope this helps.

We'll review the new logs. Thank you.

Melissa Snyder

https://community.logos.com/discussion/comment/196821#Comment_196821

Martin ~ Have you seen any improvement with 4.2a RC 1?

Martin Folley

https://community.logos.com/discussion/comment/224794#Comment_224794

Thank you for the question and follow up

Yes the problem seems to have gone.

I cannot remember when though.

My current version is "Logos Bible Software 4.2a (4.21.5.0585) (Update Channel: beta)"

Is that the same as RC1? L4Mac has not offered and update, so I presume it to be the latest.

Regards

Martin.

Graham Criddle

https://community.logos.com/discussion/comment/224910#Comment_224910

Hi Martin

My current version is "Logos Bible Software 4.2a (4.21.5.0585) (Update Channel: beta)"

From http://wiki.logos.com/Mac_Release_Notes_and_History#Mac_Beta_Release_Notes_and_History this is indeed 4.2a RC1

Graham

Jack Caviness

https://community.logos.com/discussion/comment/224910#Comment_224910

My current version is "Logos Bible Software 4.2a (4.21.5.0585) (Update Channel: beta)"

Is that the same as RC1? L4Mac has not offered and update, so I presume it to be the latest.

Logos does not include the RC designator in the name in case this becomes the release version.