Bug L4.2a
Just last night I had a small problem with a crash.
Comments
-
Do you recal what you were doing when this crash occurred? If so please describe the steps you took to cause the crash. Have you been able to repeat the crash, or was it a one time occurrence?
0 -
As to what had happened, I had been studying for my sermon when I finally finished for the evening and had decided to read a book before going to bed, I didn't close the other books in my layout not really thinking there could be a problem. the books i had open were
- KJV 1900
- NASB 1995
- KJV 1900
- Search
- Search
- Spirit Filled Life Study Bible
- Sermon Note File
- The Beloved Disciple's Memoirs The Gospel of John I, II, and III (I "floated that tab and enlarged it)
- Text Comparison
- Passage Guide
- Passage Guide (On a seperate scripture)
- Copy Bible Verse
I had studied that evening using those books then without closing them I opened the book "character forged from conflict" l enlarged it to paged view and started reading. in a short time Logos stopped working and was forced to close.
Yes I have been able to reproduce it and here is the log file from that one.
0 -
I opened everything listed except for the "Spirit Filled Life Study Bible" because I do not have that resource. Then I opened the book you and enlarged it to page view. I did not get a crash.
I guess the developers will have to look at you logs to see what is going on.
0 -
If only there was a way to send you the "layout" [:S] I just hope if this is a problem we can get it fixed.
It's easy to avoid but it is something that will happen to someone else down the road somewhere I fear.
0 -
You can take a screen shot of the layout and post it if you like.
I am sure the logos folks are reviewing the logs posted and if there is a problem in the program they will get a fix in place.
0 -
Wesley ~ I've submitted your log to development. Thanks.
Update: Development is asking if you will collect a crash dump to help them troubleshoot this crash. Please follow the instructions here: http://wiki.logos.com/ProcDump. The crash dump files can be very large, even when zipped. If the zipped file is not too large to email, you can email it to logos4feedback at logos.com. If it's too large to email, please let me know, and I will ask a support technician to contact you to do a file transfer.
0 -
Melissa Snyder said:
Update: Development is asking if you will collect a crash dump to help them troubleshoot this crash. Please follow the instructions here: http://wiki.logos.com/ProcDump. The crash dump files can be very large, even when zipped. If the zipped file is not too large to email, you can email it to logos4feedback at logos.com. If it's too large to email, please let me know, and I will ask a support technician to contact you to do a file transfer.
Melissa, I am new to procDump I went to wiki to look at the howto but I am just a bit confused about how to do the command prompt.
0 -
Wesley Crouch said:
I am just a bit confused about how to do the command prompt.
Start | ALL Programs | Accessories. Right click Command Prompt and Run as Admin.
You can copy the ProcDump command and paste it into the Command Prompt by clicking on the little icon at top left, choosing Edit and then Paste.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Start | ALL Programs | Accessories. Right click Command Prompt and Run as Admin.
You can copy the ProcDump command and paste it into the Command Prompt by clicking on the little icon at top left, choosing Edit and then Paste.
Dave,
I have opened Command Prompt several times copied the command listed as follows
cd UNZIPPATHprocdump -e -x "%LOCALAPPDATA%\Logos4\System\Logos4.exe" Logos4.dmp
it is the UNZIPPATH that i am having a problem with the folder the procdump file is in is located at C:\Users\Wes\Documents\procdump[1] and I have tried various ways to make the command right but no luck. Can you please help? I need to learn it [:^)]0 -
Type:-
- CD
C:\Users\Wes\Documents\procdump[1] - Enter
Assuming that procdump[1] is a valid folder the Prompt should now look like
C:\Users\Wes\Documents\procdump[1]>Type (or paste):
procdump -e -x "%LOCALAPPDATA%\Logos4\System\Logos4.exe" Logos4.dmp- Enter
Dave
===Windows 11 & Android 13
0 - CD
-
Dave Hooton said:
Assuming that procdump[1] is a valid folder the Prompt should now look like
I suspect procdump[1] is the filename, not the foldername. In which case the commands are just:
- CD
C:\Users\Wes\Documents [ENTER] procdump -e -x "%LOCALAPPDATA%\Logos4\System\Logos4.exe" Logos4.dmp [ENTER]<br />
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 - CD
-
AT LAST! Sorry for shouting but it was for happiness! [:D] I sent the dump file to logos at the address that was listed above.
Thanks for helpiing me get started with procump! I guess I was just a bit simple minded!!!!
0 -
Wesley Crouch said:
AT LAST! Sorry for shouting but it was for happiness!
I sent the dump file to logos at the address that was listed above. Thanks for helpiing me get started with procump! I guess I was just a bit simple minded!!!!
We received the file and development will review it. Thank you.
0 -
Can you reproduce the problem by having only Character Forged from Conflict open (and no other resources/windows open), then switching it into paged view? If so, what page was it open to before the crash?
If that doesn't reproduce the problem, are you able to find a simple set of steps that do reproduce the problem?
0 -
Bradley Grainger said:
Can you reproduce the problem by having only Character Forged from Conflict open (and no other resources/windows open), then switching it into paged view? If so, what page was it open to before the crash?
If that doesn't reproduce the problem, are you able to find a simple set of steps that do reproduce the problem?
By itself Character Forged from Conflict open and switched to paged view causes no crash I've tried it over and over.
to reproduce the crash I just open to a certain layout I have attached the snippings of both pages. When I go to paged view it crashes. I thought there were too many pages open but I tried it again shutting down some of the layout only to have the same crash.
0 -
I've been able to reproduce a crash by adding a note to a paragraph in The Beloved Disciple's Memoirs (as shown in your screenshot). We'll try to fix this in the next beta; in the meantime, you may be able to work around the crash by not using paged view or full-screen reading view in that resource (or perhaps by closing that resource before putting a different resource into paged view; I'm not totally sure of all the ways this crash can happen yet).
0 -
This bug has been fixed in 4.2a Beta 7.
0 -
Bradley,
I want to thank you and all the people at Logos for the new update the bug has been fixed and all is well!
God bless you all!
0
