Crash 5.3 Beta 1 while rebuilding a PB - no crash or error logged
I ran the beta (in German UI - the installer seems to default to that automatically based on my OS language) and told L5 to (re-)build a personal book I has accessed before [noting a) my PBs where still there from the method 2 install and b) I could access the *.docx files even though they are in the user folder of my other user on this machine). L5 closed the panel where it was visible and started building the book. So far fine.
Then Windows told me "Logos had an error and needs to close". Whoop - gone. Of course I checked the logs: no crash log, no entry to the error log, no entry to the PBB log. The logos.log simply had stopped at 20:16.
The indexer was still working and is working as I write.
Have joy in the Lord! 
Comments
-
The crash seems to be repeatable.
Logs:
what Event Viewer told me (includes WER file):
does .NET 1026 tell anything?
Have joy in the Lord!
0 -
Is it the same source document posted here (http://community.logos.com/forums/t/37714.aspx) or have you made local modifications?
0 -
Bradley Grainger (Logos) said:
Is it the same source document posted here (http://community.logos.com/forums/t/37714.aspx) or have you made local modifications?
It is, but that's not the issue. I can repeat the same error with another book (rebuild or new-build, no matter).
EDIT: the error also occurs in the English UI, it is repeatable in both my beta 1 installations and for various types of PBs and it also occurs when I run Logos 5 "as adminstrator". It seems there's simply no way for me to build a PB under 5.3 Beta 1.
Have joy in the Lord!
0 -
I think we'll need a native crash dump to diagnose the problem. Download ProcDump from http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx, then run:
procdump -e -x C:\Users\Mick\AppData\Local\Temp C:\Users\Mick\AppData\Local\Logos5\System\Logos.exe
Compile the personal book and wait for Logos to crash. ProcDump should display a message about capturing the dump, then it will write it to %TEMP%. Email the dump file to LogosBugs@logos.com (or put it in Dropbox/Google Drive/etc. and send us the link).
0 -
Hi Bradley; I have discovered that I am affected by this bug also (same issue) using 5.3 Beta 1. Will you need the dump file from me as well?
Windows 7 64 Ultimate with 8M memory. English system.
Thanks
0 -
Bump
How shall I proceed (if I should proceed at all)? Any idea what may be going on here?
Thanks
0 -
The more the merrier - just email the procdump when completed.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
The more the merrier - just email the procdump when completed.
Thanks Dave; I was trying to get away without the need to produce that file. It's been a real pain to produce, but I guess there is no other way. [:)]
0 -
Okay, I managed to create an output from the Procdump, but not sure if it completed correctly. This is what I get (also emailed this to the address listed in this thread). Thanks
ProcDump v7.0 - Writes process dump files
Copyright (C) 2009-2014 Mark Russinovich
Sysinternals - www.sysinternals.com
With contributions from Andrew Richards
Process: Logos.exe (7828)
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: 10
Hung window check: Disabled
Log debug strings: Disabled
Exception monitor: Unhandled
Exception filter: *
Terminate monitor: Disabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 1
Dump folder: d:\temp\
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS
Press Ctrl-C to end monitoring without terminating the process.
CLR Version: v4.0.30319
[23:30:40] Exception: E0434F4D.System.IO.FileNotFoundException ("Included file not found: C:\Users\estull\Documents\Logos Log Files\Logos4.NLog.config")
[23:30:59] Exception: E0434F4D.Libronix.Utility.Net.WebServiceException ("Status code not handled.")
[23:30:59] Exception: E0434F4D.Libronix.Utility.Net.WebServiceException ("Status code not handled.")
[23:31:02] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (304) Not Modified.")
[23:31:12] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (304) Not Modified.")
[23:31:44] Exception: E0434F4D.System.FormatException ("Unable to load position for resource: LLS:29.3.5, parameters: Article=THEBLESSINGSOFOURJUSTIFICATIONROM51-11|ArticleLength=7237|Context=vv.%203?4).%20Justificat|Offset=2988|OffsetInContext=10|Resource=LLS:29.3.5|Version=2007-05-01T22:22:09Z")
[23:31:44] Exception: E0434F4D.System.FormatException ("Unable to load position for resource: LLS:29.3.5, parameters: Article=THEBLESSINGSOFOURJUSTIFICATIONROM51-11|ArticleLength=7237|Context=cter?hope.%20Our%20Engli|Offset=3478|OffsetInContext=10|Resource=LLS:29.3.5|Version=2007-05-01T22:22:09Z")
[23:31:57] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:57] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:58] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:31:59] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:00] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:01] Exception: E0434F4D.System.Net.WebException ("The remote server returned an error: (404) Not Found.")
[23:32:38] Exception: E0434F4D.System.AccessViolationException ("Attempted to read or write protected memory. This is often an indication that other memory is corrupt.")
[23:32:39] The process has exited.
[23:32:39] Dump count not reached.0 -
Erwin Stull, Sr. said:
Okay, I managed to create an output from the Procdump, but not sure if it completed correctly.
I think there's a bug in ProcDump 7.0 that prevents it from capturing dumps from Logos.
For now, please wait until 5.3 Beta 2 is released, and see if you can reproduce the problem with it. We already fixed some crashes in PB compilation internally, and this may address your problem.
0 -
would trying to capture it with the old version from 2013 help you?
Have joy in the Lord!
0 -
Bradley Grainger (Logos) said:Erwin Stull, Sr. said:
Okay, I managed to create an output from the Procdump, but not sure if it completed correctly.
I think there's a bug in ProcDump 7.0 that prevents it from capturing dumps from Logos.
For now, please wait until 5.3 Beta 2 is released, and see if you can reproduce the problem with it. We already fixed some crashes in PB compilation internally, and this may address your problem.
Thanks Bradley; Somehow I'm thinking that we had this issue (or something very similar) long ago in the L4 days, but can't recall when or how it was fixed. Searching my emails to see if there is anything concerning it, but I may have phoned it in at that time. Will wait for B2.
0 -
NB.Mick said:
would trying to capture it with the old version from 2013 help you?
Yes, ProcDump 6.0 still works. But let's wait and see if Beta 2 fixes it.
0 -
Have joy in the Lord!
0 -
It looks like this has been fixed in Beta 2. Thanks Logos.
0
