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?
Here is Logos4Error.
8306.Logos4Error.log.
Sorry David, but that does not have anything for Beta 8. Nor can I reproduce the crash.
See http://wiki.logos.com/Diagnostic_Logging
I am still getting the same crash quite often. Please let me know how I can create log files that will help to debug the problem.
Please let me know how I can create log files that will help to debug the problem.
David
The link in my previous post will show you how to do that. Repeat the crash in beta 9 and upload logos4.log and any crash/error logs.
I followed as best as I could what was in the link under 4.5 Beta 9. It crashes but it does not create logos4crash log. Can you take control of my computer remotely and to see what I'm doing wrong not being able to create the crash log?
So you tried to install Beta 9?
Try starting L4 with CTRL key held down. If it crashes go to \Documents\Logos Log Files\ and upload any recent files e.g. logos4error.log, logos4.log.
Here is a error log under Beta 9.
4744.Logos4Error.log
I tried to create Logos4crash.log by starting up with CTRL key down and turning on error logging permanently as explained in the link. I could not get one. I sent logs from Logos4 and Logos4error earlier and you could not help.
I sent logs from Logos4 and Logos4error earlier and you could not help.
Still need to see logos4.log. This should be available if you can get into Logos 4 to reproduce the error when reading KJV1900.
Here are the logs after a crash.
1452.Logos4.log
3527.Logos4Indexer.log
0486.Logos4Error.log
4048.logos4setup.log
6278.Logos4Crash.txt
It appears that a Logos4Crash log wasn't created as a result of this crash (this happens occasionally). I will send your Logos4.log file to our Development department and enter a case.
Does this happen just with the KJV 1900 or with other books as well?
David, can you please follow the instructions on http://wiki.logos.com/ProcDump to collect a native crash dump? This will help us narrow down the issue.
Procdump did not work.
David,
Does the C:\DAVID\PROCDUMP\Logos4_111215_122629.dmp exist on your system?
Yes, I zipped the file and ready to e-mail. What will be the e-mail address?
The dump was created even before Logos4 was fully initialized. The dump is not from the problem that I am reporting.
What will be the e-mail address?
Please send it to logos4feedback@logos.com
I e-mailed those files.
Here are the logs from the last crash.
2161.Logos4Indexer.log
1581.Logos4.log
5381.Logos4Error.log
I had CTRL-key pressed while LOGOS 4 started. But I do not see the crash log anywhere.
Thank you,
I have forwarded your logs (along with the dump log you mailed) to our Development department.
According to the crash dump, the "windir" environment variable is missing on your system.
This should usually be set to C:\Windows
To fix this, open the Start menu and type "environment" into the Search box. Choose "Edit the system environment variables" from the list of programs that appears. Click the "Environment Variables" button to open the Environment Variables dialog. Scroll to the very bottom of the "System variables" list. If my diagnosis is correct, there will be no "windir" entry in the list. To create it, click "New...". Enter "windir" for the name and "C:\Windows" for the value. Click OK to close all the dialogs, and restart Logos 4.
If you still get problems paging through the resource, please collect another crash dump; this crash may have masked the real problem (as you suspected, because it crashed so early).
windir was there. There must be another reason for the crash.
Agreed, but we can't diagnose the problem until we obtain a crash dump of this crash.
How can I get a crash dump? I followed as best as I can the instructions that were given.
Hello David,
Just following up - did setting the "windir" environment variable on your system fix this issue?
Windir was there. It was not the cause of the crash. I did not need to add the line into the environment.
Understood, and thanks for letting us know. If you experience the crash again we'd like to take a look at any fresh crash dumps you might have.
I get the crash almost daily. I need help to get a crash dump. I followed instructions as best as I could. I pressed CTRL key while Logos started. I turned on permanent diagnostic dump. Nothing helps. I wanted to have someone to capture my screen and check settings to see why I can not get a crash dump.
David, you got one crash dump as per the screen capture you posted, so let me guide you a little:
Thank you for your suggestions. But the procdump crashed before I can reproduce the crash as I discussed earlier.
Here are logs after the crash under 4.5 B11. Again, there is no error or crash log.
144581.Logos4.log
7446.Logos4Indexer.log
6076.logos4setup.log
4331.DigitalLibraryInstall.log
Curious if procdump is version 4.01 ?
Looking at Logos4.log, noticed lot of sync updates, updloading, and downloading.
Wonder about restarting computer, check that indexer is not running, then in a command prompt: echo %windir% If Windows path appears, then try using procdump again. Once Logos 4 launches, suspect sync arrows will be turning, suggest waiting for sync arrows to stop. If sync completes without crashing, then try reading KJV 1900.
Keep Smiling [:)]
Procdump is 4.01. echo %windir% retunrns %windir% not windows path. Procdump keeps crashing before Logos is fully loaded. It appears that the crash has to do with sync as you suspect. The last entry in logos4.log is sync of note files. The sync is periodically done. It never completes.
I can read KJV1900 quite a few chapters before it crashes. But I can recreate the crash almost all the time as long as I read it long enough.
As far as I can remember, this problem was introduced after the release of 4.5 beta cycle not necessarily at beta 8.
Typing echo %windir% from a command prompt should return something like "C:\Windows" (assuming your Windows install is on drive C:\). If you type "set" from a command prompt does "windir=C:\Windows" appear somewhere? If not, there is indeed something wrong and %windir% is not properly set.
Procdump is 4.01. echo %windir% retunrns %windir% not windows path.
In a command prompt, set shows all environment variables:
If an environment variable is set, then echo %variable% shows the value, otherwise echo repeats the character string.
The environment variable, windir, is a default system variable for Windows:
One way to edit system environment variables is: right click on Computer => Properties (to open System control panel)
In System control panel can click => Advanced system settings
It is strange indeed. echo %USERNAME% returns David not SYSTEM. %TEMP% returns c:\Users\David\app... not c:\windows\Temp. echo %windir% returns %windir%. All other variables in System variables returns Value except windir. I added windir variable in User variables and restarted the computer to see if it makes difference. It still returns %windir%. I am running as an administrator.
echo %windir% returns %windir%
It would appear that the environment inside the Command Prompt is incorrect (not sure how). However, you should still be able to run a program directly from the Start menu, without launching a Command Prompt first.
Press Windows+R, then enter
C:\Path\To\ProcDump.exe -e -x "%LOCALAPPDATA%\Logos4\System\Logos4.exe" C:\Temp\Logos4.dmp
Hopefully this should let Logos 4 run normally (until you reproduce the crash), and it will write the dump to C:\Temp. (Change the path as appropriate for your system.)
Followed the instruction and got a message "Do you want to run this file .... procdump" When I selected "Run" option, a command screen appears briefly (less than a second) and disappeared. I cannot find a dump anywhere and Logos4 never started.
When you paste the exact same command-line (from the Windows Run dialog) into a command prompt, what happens?
Alternative: Launch Logos 4 as normal. When it's loaded, run (from a command prompt):
procdump -e logos4.exe
Reproduce the crash. ProcDump should now have created a crash dump file for Logos 4.
When I paste the exact same command-line into command prompt, it creates the same error as before (%windir% problem?). I started Logos4 and initiated procdump. Procdump was running in a command window as long as Logos4 was running. When Logos4 crashed, the window disappearted at the same time. There is no indication that it created a dmp file. I searced for logos4.dmp and *.dmp on the c:\ drive. I could not find any dmp file from the crash.
Here is the screen shot of the window for KJV. When I repeatedly pressed space bar to recreate the crash, Logos4 handled it well and never crashed. When I read it slowly page by page, it will crash at some point sometimes after a few chapters other times after many chapters. But it will crash at some point. I'm running Windows 7 home premium.
There is no indication that it created a dmp file. I searced for logos4.dmp and *.dmp on the c:\ drive. I could not find any dmp file from the crash.
Run
procdump -e logos4.exe C:\Temp\logos4.dmp
(replace "C:\Temp" as needed)
ProcDump should save the file in the C:\Temp folder. If you run it from a command prompt, it should print out where it wrote it before it exits.
It took over an hour and half to recreate the problem this time.
Here is the screen capture of procdump after the crash. It appears that Logos4 terminates immediately without generating an error condition.
I turned off "Use Internet" and "Automatic Update" to see if it makes difference. It still crashed the same way as before.
The C:\ folder typically isn't world-writable, so it's likely that procdump would fail to save a dump file there. Please choose a folder that your user account can write to (C:\Users\David should work).
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.
Just poking my nose in ... please excuse me if these ideas are not helpful:
Does the C: drive have free space?
Does chkdsk c: run clean on the drive?
Does the Windows Event Log report anything suggestive around the times in question?
I wish I could sit there with you for a short while. Its possible this could sort out, but its hard to know what ideas to suggest from half a world away.
Regards, Jim
