Logos 4 hangs frequently - requires killing with taskmanager
I have a core 2 duo with 4 G of ram. Logos frequently hangs when performing the most basic activities. I will wait for several minutes, but the app is dead and requires killing it with the taskmamager.
These activities are navigation related. The app hangs following scrolling a bible window with a mouse wheel, or changing verses with the search control.
I tend to link as many resources as possible, is this stressing the application too much?
Are there certain tools that should not be left open during navigation?
Does Logos test their software extensively, or do they just make sure that a few basic scenarios work?
In any case, it would seem that Logos needs to add stress testing to their process.
I am disabling all links between the books, since this is probably stressing the software.
As a software professional, I understand the momemtum and pressures - the GO FEVER to ship a product with new features and such and how the bar for bugs can be low for the sake of getting the product out the door.
When is the service pack coming out to fix these bugs, or are the bugs in the underlying technologies?
Comments
-
The Cited by tool when set to follow is notorious for slowing Logos down to a crawl. 4.0b (which just hit RC-1 yesterday) has customization features for this tool that help mitigate its drain on resources.
Other than that I'm not qualified to answer your question about how Logos tests its software in house. I too would be interested to hear their responses to your questions about stress testing.
For the benefit of the developers working on Logos you might want to consider reproducing Logos locking up and submitting logs (http://wiki.logos.com/Diagnostic_Logging http://wiki.logos.com/Uploading_Logs ).
Prov. 15:23
0 -
I am having the same problems with Logos locking up. How do I follow your advise and reproduce logs?
0 -
jkrauss@astound.net said:
I am having the same problems with Logos locking up. How do I follow your advise and reproduce logs?
Follow the links in my post, they will provide directions.
Prov. 15:23
0 -
stevemac@microsoft.com said:
I have a core 2 duo with 4 G of ram. Logos frequently hangs when performing the most basic activities. I will wait for several minutes, but the app is dead and requires killing it with the taskmamager.
These activities are navigation related. The app hangs following scrolling a bible window with a mouse wheel, or changing verses with the search control.
I tend to link as many resources as possible, is this stressing the application too much?
Are there certain tools that should not be left open during navigation?
How many panels are you linking together? Which tools do you have open? A log would help to understand what is causing the crash.
0 -
If you haven't gotten a million complaints and are asking me for log files, then I must be hitting a corner case, more likely, I have too many links to big content that is stressing the system.
I am new to Logos - really I don't know you folks. I am a longtime bibleworks user and am quite willing to help them with bugs because they do their best to keep their prices down and keep their quality high. Logos seems more commercial and I don't really care for your licensing agreement for content and I havn't cared for some of the rhetoric about books being obsolete and getting rid of the bibleworks "people in the basement" attitudes I am hearing from the community.
Maybe after I get to know you folks, I might send some logs, but in the meanwhile, I am just passing this along as a friendly gesture.
0 -
stevemac@microsoft.com said:
I havn't cared for some of the rhetoric about books being obsolete and getting rid of the bibleworks "people in the basement" attitudes I am hearing from the community.
There are just a handful of real problem people ... no more than the general population. When the switch was made from newsgroups to forums the number of participants expanded greatly; unfortunately, this included some who were unfamiliar with standard forum etiquette but they are learning quickly. If you've worked in or with software companies, you know that relating a problem without giving them the information to identify the culprit isn't particularly helpful. Couldn't hurt much to send some logs and get to know us.
BTW, I've gotten several crashes with this RC but no hanging.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
stevemac@microsoft.com said:
I am new to Logos - really I don't know you folks.
Welcome, most us are harmless,except me..
stevemac@microsoft.com said:I am a longtime bibleworks user and am quite willing to help them with bugs because they do their best to keep their prices down and keep their quality high. Logos seems more commercial and I don't really care for your licensing agreement for content and I havn't cared for some of the rhetoric about books being obsolete and getting rid of the bibleworks "people in the basement" attitudes I am hearing from the community.
Sorry if thats what you think, most if us are normal users and are as passionate of paper as we are of the technology, you'll find most of us dont mention the "B" word, not because we dislike it, we acknowledge there are other tools out there, and some of us actually use other/multiple programs...
However given that this is the Logos community, its natural to expect some passion about their software over other competitors. I imagine the "B" forum to be the same, however I think you are hearing the tiny minority, I havent read a post like that for a while.. thankfully..
stevemac@microsoft.com said:I might send some logs, but in the meanwhile, I am just passing this along as a friendly gesture
Please do, its like you ringing boeing and saying theres a fault on the 747, without the logs bugs/issues are notorious/almost immpossible to trace.
stevemac@microsoft.com said:Maybe after I get to know you folks
One again, please hang aroung and get to know the real us, we don't normally bite..
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
This isn't just about the general public, Logos has their resident PhD blogging about how he sold all of his books and now has a totally electronic library.
This sort of blogging whether intentional or not attempts to justify the escalating costs of Logos electronic titles versus print copy. If the public buys into that, then the market will bear the increase.
Just as you have the right to advertise your product and reap the profit that the market will bear just as I have the right to push back on the rhetoric.
Logos is extremely slow and crashes often. I will continue to buy hard copy commentaries until Logos brings the price more inline with the return on investment.
0 -
stevemac@microsoft.com said:
This sort of blogging whether intentional or not attempts to justify the escalating costs of Logos electronic titles versus print copy. If the public buys into that, then the market will bear the increase.
Just as you have the right to advertise your product and reap the profit that the market will bear just as I have the right to push back on the rhetoric.
Yes, Logos books are more expensive than their paper siblings (base packages excluded). Whether this increased cost is justified has been debated considerably on these forums. If Logos books don't give enough extra functionality and value for the increased costs then buy paper at whatever discount you can get.
These posts on the issue of pricing by Logos' CEO may or may not interest you.
http://community.logos.com/forums/p/6745/55131.aspx#55131
http://community.logos.com/forums/p/11152/89187.aspx#89187
http://community.logos.com/forums/p/11152/88865.aspx#88865Regarding going through the process of producing and submitting logs. Yes, it might help Logos in a way that you don't seem willing to do right now, but there might be a tweak that you can perform on your machine to make it run Logos better. There are plenty of people here that are willing to try to help, if you let us.
Finally, let me just add to the chorus, welcome to the forums!
Prov. 15:23
0 -
Thanks for the perceptive reply.
0 -
stevemac@microsoft.com said:
If you haven't gotten a million complaints and are asking me for log files, then I must be hitting a corner case, more likely, I have too many links to big content that is stressing the system.
I am new to Logos - really I don't know you folks. I am a longtime bibleworks user and am quite willing to help them with bugs because they do their best to keep their prices down and keep their quality high. Logos seems more commercial and I don't really care for your licensing agreement for content and I havn't cared for some of the rhetoric about books being obsolete and getting rid of the bibleworks "people in the basement" attitudes I am hearing from the community.
Maybe after I get to know you folks, I might send some logs, but in the meanwhile, I am just passing this along as a friendly gesture.
Steve Mac, seeing as you posted a problem I am only here to try to help you out so you can get past this. In order to do so we need to evaluate what is actually going on. If you do not wish to provide logs after the crash then maybe you can at least tell us how many panels you have linked and which panels you have open, or even better provide steps so I can try to reproduce this issue - at the moment I cannot.
We need to know how much Logos4 is hindering your work so we can identify the seriousness of this issue - does it happen only when you hit a certain number of linked panels or when you have certain resources open? Please consider reproducing and posting the crash logs it will only take a moment to post them in your reply and since you have worked in development before I am sure you can understand the value your corner case will give us. Maybe the crash you are experiencing is a completely new bug, maybe not, but we are approaching the end of the release cycle and it would really help *everyone* out.
0
