Pressed a space bar to go to the next page while reading KJV 1900. I started the Logos with Ctrl key down. But there is no Logos4Crash file to upload. How do I create the file?
Logos exited immediately when I recreated the error. Procdump did not generate a dump. This is quite strange. I'm not sure why procdump isn't capturing a dump of this crash, but unfortunately without the crash file, we can't perform any diagnosis of this issue. Some suggestions: try turning off visual filters and highlighting in that resource; switch from paged view to scrolling; use the default font and size; disable inline interlinear display; turn off "Show footnotes on page". One or more of these settings may be causing the crash on your system.
Logos exited immediately when I recreated the error. Procdump did not generate a dump.
This is quite strange. I'm not sure why procdump isn't capturing a dump of this crash, but unfortunately without the crash file, we can't perform any diagnosis of this issue.
Some suggestions: try turning off visual filters and highlighting in that resource; switch from paged view to scrolling; use the default font and size; disable inline interlinear display; turn off "Show footnotes on page".
One or more of these settings may be causing the crash on your system.
Hello David,
I haven't forgotten about you! We just released 4.5 Beta 14 tonight - I suggest you first upgrade to that version (if you can) and if the same issue occurs on your system, please follow Bradley's steps if possible and let me know what happens.
Nobody else is experiencing the issues you've suffered through, and I'm beginning to think this is a possibly a Windows OS corruption problem. Procdump is a Microsoft tool designed to dump process information after a crash, but if that doesn't work properly it's another indication that your computer might need a fresh install of Windows.
In any case I'll keep following this thread so please keep us updated.
I started a command window and entered SET WINDIR=C:\WINDOWS command. Then, ECHO %WINDIR% returned C:\WINDOWS. I could start LOGOS from PROCDUMP. Logos ran very slow in that mode. It delayed considerable amount of time every few pages before turning to the next page when I pressed space bar. I could not reproduce the problem in that mode even though I tried a few hours. I open three windows when I read KJV according to McCheyne's reading plan, KJV, Reading Plan, and Copy Bible Verses. I can reproduce the problem only when I start Logos without Procdump. When I start Logos first and let procdump watch Logos process, Logos terminates immediately without producing a dump.
Are you running any anti-virus software or have you attempted to remove any possible malware that might be affecting your system? I'm curious - are you experiencing any other crashes with non-Logos software?
Yes, it is protected by antivirus software. Full scan returned no warning. No other programs crash as regurarly as logos does. Logos runs quite a while before it crashes.
When I close other windows (Bible reading program and Copy Bible Verses), I can not reproduce the crash. It appears that Logos 4.5 RC1 crashes only when there are multiple windows open. Even when other windows are open, it takes long time to reproduce the crash. I can read quite a few chapters before Logos crashes.
Hi David,
Your best bet now is to contact customer support if you run into any issues since 4.5 RC1 is an officially supported version.
Hi David, Your best bet now is to contact customer support if you run into any issues since 4.5 RC1 is an officially supported version.
Shouldn't that information be available to the L4 Forums as the 4.5 RC threads only state that it is available for testing?
Hi David, Your best bet now is to contact customer support if you run into any issues since 4.5 RC1 is an officially supported version. Shouldn't that information be available to the L4 Forums as the 4.5 RC threads only state that it is available for testing?
I apologize - "officially supported" may have been too strong of a wording. An RC is considered a stable version but you will want wait until it ships to the stable channel and then call customer support if necessary. Sorry for confusing the issue.!
