Several crashes
I've been using the program lightly for 3 days with no problem, but suddenly I'm having a cluster of crashes. Log files attached. I did not submit to Microsoft because that window did not come up for me.
Description
Crash when opening a custom guide, closing a custom guide, and moving frames within Logos.
Repro
- Open Logos 4
- Click on "Guides" and select my custom guide
- Logos crashes
- Open Logos 4
- Open custom guide
- Edit custom guide
- Click on drop down menu on guide
- Logos crashes when I click "close"
- Open Logos 4
- Open guide, Bible, and Cross References in three panes
- Try to switch the location of two of the panes
- When I let go of mouse button, Logos crashes.
System Specs
- Windows Vista 64 on a desktop, Intel core i7, 6GB RAM, nVidia G220 with1GB
Comments
-
TimothyLovegrove said:
I've been using the program lightly for 3 days with no problem, but suddenly I'm having a cluster of crashes. Log files attached. I did not submit to Microsoft because that window did not come up for me.
Description
Crash when opening a custom guide, closing a custom guide, and moving frames within Logos.
Repro
- Open Logos 4
- Click on "Guides" and select my custom guide
- Logos crashes
- Open Logos 4
- Open custom guide
- Edit custom guide
- Click on drop down menu on guide
- Logos crashes when I click "close"
- Open Logos 4
- Open guide, Bible, and Cross References in three panes
- Try to switch the location of two of the panes
- When I let go of mouse button, Logos crashes.
System Specs
- Windows Vista 64 on a desktop, Intel core i7, 6GB RAM, nVidia G220 with1GB
Do you have the latest video drivers?
By crash we mean that the program hangs indefinitely (sometimes appearing as a black screen or a see-through window) and having the 'Not Responding' attached on the title bar AND the microsoft error reporting dialog pops up. If the dialog doesn't pop up, then the program is hanging and will probably respond shortly. If it hangs indefinitely and the error reporting window doesn't come up (i would say to try 1 minute, then 3 minute waits) then it is as good as a crash bug. Please try to repro with that in mind and let me know your progress.
0 -
I'm sorry, I guess I wasn't very clear. What happens is that the program just suddenly closes and is gone. There is no black screen, no frozen program, no locked-up Logos. It's just gone, and I have to reopen it and restart what I was doing.
It has happened several more times since I posted, so I can send updated logs if needed.0 -
0
-
I started it again this morning, opened my layout, set the resources to link set A, changed the passage in the Bible, and it crashed. Screen shot and logs attached.
0 -
-
TimothyLovegrove said:
I started it again this morning, opened my layout, set the resources to link set A, changed the passage in the Bible, and it crashed. Screen shot and logs attached.
Can you provide a clear step by step repro? Please include what resource panels the layout opened, which resource you set the link set in, which bible you were using, and which passage you changed to. And for the screen shot it would help to show a screenshot of the layout or the panel menu which you were switching to link set A, usually a screenshot of the crash dialog itself doesn't tell us much.
0 -
George Allakhverdyan said:
Can you provide a clear step by step repro? Please include what resource panels the layout opened, which resource you set the link set in, which bible you were using, and which passage you changed to. And for the screen shot it would help to show a screenshot of the layout or the panel menu which you were switching to link set A, usually a screenshot of the crash dialog itself doesn't tell us much.
George, I'm sorry I'm not giving you quite what you need. Attached is a screenshot of my setup before the crash under discussion. I'm sorry but I don't remember the exact passage I was going to when it crashed, but I know that I entered the passage in the NASB95 pane.
So the repro would be:
open v.4
select custom layout
layout = custom guide, NTSK, and NASB95
set all to linkset A
change passage in NASB95
crashI will be very careful to repro the exact details of future crashes for you.
0 -
0
-
George,
A bunch more crashes. Logs attached. Actually what happened is that it crashed, and I kept trying to go back and get you a screen shot of the setup, but it crashed over and over (at slightly different points) as I tried to set it up. Here's the repro of the first time:
v.4 open to a custom layout with custom guide, NTSK, and NASB95.
set all to linkset A
search "Ezra 10:2-5" in Custom Guide
Try to switch the "word for word" section from BHS/WTS 4.0 Morph to NASB95 Reverse Interlinear
crash as soon as I click "NASB95 Reverse Interlinear"Then I kept trying to get back to that screen, and it crashed again at that point, then it would crash earlier as I set the key links, etc. I can't remember how many times it crashed. So no screen shot available, because I can't get back to that point.
0 -
FYI If I change the order up, and it allowed the switch to NASB R.I. , and didn't crash until I did the linksets. I.e., it may well have something to do with the linksets:
open custom layout with custom guide, NASB95, and NTSK
search Ezra 10:2-5 in custom guide
set linksets to A - when I select the third linkset (NTSK), it crashed0 -
Description
Program crashed.Repro
Had collections screen open
Tried to open LibraryActual Result
Program crashedSystem Specs
Laptop with Windows Vista Business Service Pack 1 32-bit OS
Intel Duo Core P8400 @ 2.26 Ghz
3 Gigs RAMLogs Attached.
Laptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
Jim Fulford said:
Description
Program crashed.Repro
Had collections screen open
Tried to open LibraryActual Result
Program crashedSystem Specs
Laptop with Windows Vista Business Service Pack 1 32-bit OS
Intel Duo Core P8400 @ 2.26 Ghz
3 Gigs RAMLogs Attached.
Hi Jim, are you able to reproduce this? Unfortunately, log file you posted isn't showing the actual error. This can sometimes happen if the program crashes before it can finish writing the log. Please keep submitting the report to Microsoft (if you are offered the option); we are collecting these crash reports and can often diagnose the underlying problem from them (though usually the log files are more helpful).
One other thing to try is clicking a rating star (on any book) or adding a tag; this causes My Library to be reindexed, which might flush out any bad data that's preventing the searching. (Depending on the speed of your computer, wait between 5-30 seconds after setting a rating for indexing to finish.)
Let me know how that goes.
0 -
TimothyLovegrove said:
George,
A bunch more crashes. Logs attached. Actually what happened is that it crashed, and I kept trying to go back and get you a screen shot of the setup, but it crashed over and over (at slightly different points) as I tried to set it up. Here's the repro of the first time:
v.4 open to a custom layout with custom guide, NTSK, and NASB95.
set all to linkset A
search "Ezra 10:2-5" in Custom Guide
Try to switch the "word for word" section from BHS/WTS 4.0 Morph to NASB95 Reverse Interlinear
crash as soon as I click "NASB95 Reverse Interlinear"Then I kept trying to get back to that screen, and it crashed again at that point, then it would crash earlier as I set the key links, etc. I can't remember how many times it crashed. So no screen shot available, because I can't get back to that point.
Hi Timothy, we received your logs and I think the devs already fixed this issue for Beta 2. Thanks.
0 -
Crash on Startup
-> Logs attachedLaptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
Hovered over reference in BDB. Program Crashed. (Program was also re-indexing at the time)
-> Log AttachedLaptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
2nnd Crash while building a collection. Log attached. (Still Indexing)
Laptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
Crash while nothing obvious is happening. Since indexer continues to
crash, I rebooted system & then L4 & when it wanted to index, I
paused it for the 4 hrs. After a couple of hours sitting and not being
used, the main program, of itself, crashed. I was using L3 since I will
have to wait for an update to L4. My indexer is still sitting there in
the system tray & counting down the time until the indexer will
start again. I'm afraid L4B3 is crashing more than L4B2. I sure
schedules are pushed, but I think L4 should be titled alpha rather than
beta. It's way too unstable at the moment. Be encouraged though. It
seems awesome to me & worth the perseverance. Keep going, I'm sure
we'll get there in the end & she'll be a super product.David
Specs: Laptop Toshiba P30; P4 3.6 ghz; 2gb RAM; 128mb video card; running XP SP3, IE8.
David
https://echucacommunitychurch.comMacBook Pro (13-inch, M1, 2020), 8 gig RAM, macOS Ventura.
0 -
David McAllan said:
Crash while nothing obvious is happening. Since indexer continues to crash, I rebooted system & then L4 & when it wanted to index, I paused it for the 4 hrs. After a couple of hours sitting and not being used, the main program, of itself, crashed. I was using L3 since I will have to wait for an update to L4. My indexer is still sitting there in the system tray & counting down the time until the indexer will start again. I'm afraid L4B3 is crashing more than L4B2. I sure schedules are pushed, but I think L4 should be titled alpha rather than beta. It's way too unstable at the moment. Be encouraged though. It seems awesome to me & worth the perseverance. Keep going, I'm sure we'll get there in the end & she'll be a super product.
David
Specs: Laptop Toshiba P30; P4 3.6 ghz; 2gb RAM; 128mb video card; running XP SP3, IE8.
Hi, this is may be due to not having installed the latest update. Can you confirm you did? If you notice a Logos blue icon in the task-bar, and if you right click on it, it will say "Install Update" or "Hide Icon", then you know you haven't installed the latest update. There was a change to excerpts and we believe this is causing your crash.
0 -
Jim Fulford said:
Hovered over reference in BDB. Program Crashed. (Program was also re-indexing at the time)
-> Log AttachedThanks for the log, looks like a new bug. Can you be specific as to what reference?
0 -
Tried to sort "Series" column while building a new collection. Program crashed. Sent report to Microsoft. Log attached.
Laptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
Crashed when right-clicking to add a column in Collection window. Log Attached.
(P.S. I Love the program!! I just use this thread to keep feeding you logs of crashes. I trust this is what you want)Laptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
Crashed when trying to move Library to a tabbed window. Log attached.
Laptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
Opened v4B4 -- Right-Clicked Library -- Opened Library in a new tab [:)] -- Changed to detailed view -- Clicked on "Type" column header to sort by type -- Program crashed & closed -- No opportunity to send notice to Microsoft -- Log attached. (Thanks)
Laptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
FYI...trying to type anything into the Library search box when it is in "List/Detail" view STILL hangs the program (now in Beta 4). I guess it must just be some other contributing factor on this laptop. I will not report this again (Unless it all of a sudden begins to work) - Log attached (I doubt anything was written to the Log though).
Laptop:Vista Business SP2 32-bit OS / Intel Duo Core P8400@2.26Ghz / 3-Gigs RAM
0 -
Jim Fulford said:
FYI...trying to type anything into the Library search box when it is in "List/Detail" view STILL hangs the program (now in Beta 4). I guess it must just be some other contributing factor on this laptop. I will not report this again (Unless it all of a sudden begins to work) - Log attached (I doubt anything was written to the Log though).
Hi Jim, thanks for the numerous crashes, I'm sorry to inform you it looks like you are closing the dialog too fast for it to write the last bit of information (the part we need!) The log files aren't containing any visible entries regarding a crash, which leads me to think that. Please give it 15-30 seconds before closing the error reporting dialog and we'll need more logs. I will make this more clear on the sticky posts
0