In the latest 2 betas, logos crashes for me after a couple of minutes of operation. Prior to the crash, it acts sluggish and the cpu is pegged.602624.Archive.zip
Jason:
What beta are you currently using? Do you have any other programs running? If so what ones? Thanks.
I came to the threads for the exact same reason-
Never hurts to give too much information-
Early 2008 Macbook Pro, 2.5 ghz intel core 2 duo with 4 gigs ram.
Launch Logos, Logos acts sluggish/spinning beachball often, even just scrolling through bible, and then crashes. Also running Mail, Webbrowser... pretty basic/standard apps.
Thoughts? Like Jason said- this has been apparent in Beta 6 (which I only just downloaded a few days ago) and Beta 7 (just now downloaded).
I'm using beta 7 now. Running standard mail apps with a couple of background apps like Evernote. Same stuff I always run. Macbook Pro 2.2 with 4gb of ram. I found that not only is my cpu pegged for a moment, but it eats up about 2gb of ram. Got a response from support that they are working on a fix but I could use a workaround so that I can prepare for Sunday. I've tried a reinstall already and I've tried working in offline mode.
Could you define "use"? I just want to know if it something big or small that takes the program to eat up much of your CPU. Also, is Logos 4 indexing at the same time?
Are you doing a search from the Go bar? If so what citation, how long of a passage? The longer the passage the longer it will take to generate and more of your computer will be used. Once you get back to me with what you are searching I'll post the case+logs.
I have probably 7 tabs open but I'm not doing any searches. As a matter of fact, every time I open logos I attempt to close all of the tabs but it crashes before I can. I've tried starting in the "blank layout" and that doesn't help either.
Oh, and it's not indexing.
That is good to know it crashes w/ blank layout. thanks. I'll post the logs.
Jason: Would you mind opening the app with a blank layout, waiting for it to crash, and then sending us those logs? With less going on, it should be easier for us to diagnose the problem.
Thank you gentlemen.166878.Archive.zip
Jason,
Can you send us this file too? /Users/jasondavidmcgrath/Library/Logs/DiagnosticReports/Logos Bible Software 4_2010-08-18-223201_Jason-McGraths-MBP.crash
Also, are you running the Windows version as well on the same Logos.com account, or just the Mac version? Just wondering...
Looks like I missed a bit... If you would like to see another log report with the crash problem, let me know, I can upload report.
Tom, I downloaded and signed into a windows machine at the office just to experiment with the windows version, but that was over a week ago, and it was only on the machine for 1 day. I'm only using macs right now, but I do have access to a windows machine at the office if I have to. Here's the report.5582.Logos Bible Software 4_2010-08-18-223201_Jason-McGraths-MBP.crash.zip
I deleted the app and manually deleted all resources and started from scratch (Reinstalling the app itself did not work). This seemed to work, even before I updated to the latest beta(8). My iMac is now having the same problem so I'll probably update it to the latest beta before trying to do a fresh install. No crashes after the fresh install (including resources) on beta 7.
Best I can tell, that didn't help me. I unchecked everything. The processor spikes but then goes down; but the ram usage keeps going up and stops in between 2.5 and 3 GB and holds steady until crash. But I'm not having any problems now on the latest beta and after a full reinstall.
