[resolved] CRASH: Running any kind of syntax search
Trying to learn to do syntax searches. Running even a very simple one crashes Logos instantly. Logs attached.
Eating a steady diet of government cheese, and living in a van down by the river.
Comments
-
There is no crash log nor indication of a crash in the detailed log. Provide details from the Windows Event Viewer and a screenshot of the syntax search.
Dave
===Windows 11 & Android 13
0 -
There is no crash log nor indication of a crash in the detailed log. Provide details from the Windows Event Viewer and a screenshot of the syntax search.
Can't do it tonight...it's on my laptop at the office. Will do tomorrow.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
There is no crash log nor indication of a crash in the detailed log. Provide details from the Windows Event Viewer and a screenshot of the syntax search.
Here's the event viewer screenshot-
Here's a SS of the syntax search-
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Hi Doc,
Can you save or copy the the relevant events to a text document and attach them to a reply? Select the error messages and any adjacent messages together, select the “Action” menu and select “Save selected events.” I'm not certain the forums will accept the file type, so if it doesn't copy and paste the individual error messages to individual text files and attach them.
0 -
Hi Doc,
Can you save or copy the the relevant events to a text document and attach them to a reply? Select the error messages and any adjacent messages together, select the “Action” menu and select “Save selected events.” I'm not certain the forums will accept the file type, so if it doesn't copy and paste the individual error messages to individual text files and attach them.
Not sure. Is this what you need?
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System><Provider Name="Application Error" /><EventID Qualifiers="0">1000</EventID><Level>2</Level><Task>100</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2015-05-29T15:59:23.000000000Z" /><EventRecordID>32998</EventRecordID><Channel>Application</Channel><Computer>D5DWBBW1</Computer><Security /></System>- <EventData><Data>Logos.exe</Data><Data>6.3.0.56</Data><Data>555f7ff6</Data><Data>Libronix.DigitalLibrary.Native.dll</Data><Data>6.3.0.56</Data><Data>555f7f98</Data><Data>c0000409</Data><Data>001d1cd7</Data><Data>173c</Data><Data>01d09a284df3d803</Data><Data>C:\Users\borenjb\AppData\Local\Logos5\6.3.0.0056\Logos.exe</Data><Data>C:\Users\borenjb\AppData\Local\Logos5\6.3.0.0056\Libronix.DigitalLibrary.Native.dll</Data><Data>abe2f9f9-061b-11e5-a636-606720d35844</Data></EventData></Event>Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Something more along the lines of this 7167.event.log
The text file is comprised of the logs from these events
0 -
I don't know where to find that, Tommy.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Here's a Microsoft article on the Event Viewer. http://windows.microsoft.com/en-us/windows/open-event-viewer#1TC=windows-7
0 -
I think that you'll need to collect a crash dump and send it to Tech Support for further progress on this issue; from what I saw in your screenshots, there isn't enough information in Event Viewer to diagnose this error.
Since the problem appears (so far) to be localised to your machine, it could be due to a corrupt syntax database. If you've got the time and bandwidth, you might wish to try deleting all *.lbssyn files, then running "update resources".
0 -
If you've got the time and bandwidth, you might wish to try deleting all *.lbssyn files, then running "update resources"
Bradley, where might I find these files? Do you have a pathway for me?
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
If you've got the time and bandwidth, you might wish to try deleting all *.lbssyn files, then running "update resources"
Bradley, where might I find these files? Do you have a pathway for me?
They are in the "Data\unique id\ResourceManager\Resources" folder under your top-level Logos folder
0 -
They are in the "Data\unique id\ResourceManager\Resources" folder under your top-level Logos folder
Thanks, Graham. Found them.
New futility- the folder says they are there-
..but when I try to delete them, the system says they aren't.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
but when I try to delete them, the system says they aren't
I'm guessing that Logos 6 doesn't like this situation. [:)]
Have you tried rebooting, to see if that clears out this Schrödinger-esque half-alive/half-dead state?
0 -
this Schrödinger-esque half-alive/half-dead state?
That's funny, Bradley.
I'll try that now.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Restart worked...they are gone. I'm now running the update resources routine.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Got this on the screen after the update-
...however, there were new files in the Resources folder-
and the homepage said this-
Before I break it again, should I simply try running the search, or do something else first?
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
bimp
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
Got this on the screen after the update-
and the homepage said this-
Most likely the updates were already download and installed before you manually checked for them (thus "no updates found" from your check).
Before I break it again, should I simply try running the search, or do something else first?
Definitely try running the search again; does it still crash?
0 -
Definitely try running the search again; does it still crash?
Crashed again, like James Dean in a convertible.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
I think we'll need to collect a crash dump to make any further headway on this issue.
0 -
I think we'll need to collect a crash dump to make any further headway on this issue.
Here's one.
(If there's one on my computer, you'll have to point me to directions on how to get it.)
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
You can use the instructions on the wiki (https://wiki.logos.com/ProcDump) or contact Technical Support for further assistance.
0 -
Hey Doc B,
Interestingly, I've been fighting with my Logos 6 program ever since the update ran last week. I had to go through tech support for the last few days, but it's still unresolved. I'm supposed to contact them tomorrow to keep looking for the answer.
Curious about something. I have discovered that if I run a syntax search in a resource for a construction that does not return any hits, it doesn't crash. But if I run a search where there are hits, it will begin to try populating the results and then crash right before they start to come up. This was the case with the Andersen-Forbes syntax database, as well as the Cascadia syntax database. It looks like you were using the OpenText NT database when you were getting crashes. Do you know if it will crash if you try to search for some construction that you know will not return any hits?
0 -
Do you know if it will crash if you try to search for some construction that you know will not return any hits?
It does not.
However, this is a chicken-and-egg question. I have a number of syntax searches that worked (returned hits) in the past, but after this crash, these SS no longer return any hits. They don't crash, but they get zero hits when I run them.
I think the whole thing is broken.
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
That's odd. These older SSs definitely returned hits before, but not now, eh?
Which Bible version(s) do you have it set to display search results in? I've noticed that the NAS95 icon shows up just as results are about to populate, and then it crashes before the first hit even appears on the screen. I don't know if my display version has anything to do with it, but I was curious about your own experience on this. Since I cannot change display version with an actual results panel up, and since the results panel never materializes because of the program stopping, I have no way to change display versions to see if it crashes again using another Bible to display with.
I've had two sessions this morning with tech and they finally got a crash dump file to analyze. Hopefully when they call back we'll have a better idea what's going wrong.
0 -
I meant "Since I cannot change display version *without* an actual results panel up...."
0 -
It turns out that both of you (Doc B and Phillip Marshall) are running the 32-bit version of Logos (and both on Windows 7). It's possible that this is a 32-bit only bug. We will investigate further.
0 -
It would be nice to discover a cause!
Maybe DocB and I are the only two people in the world running 32-bit on 7.
Thanks for your help!
0 -
It would be nice to discover a cause!
Maybe DocB and I are the only two people in the world running 32-bit on 7.
I do and I can replicate the bug. Logs to follow.
Have joy in the Lord!
0 -
It's possible that this is a 32-bit only bug. We will investigate further.
Bradley, I tried running Procdump 7.1 as instructed in the wiki page (had to take out folder 'system' in the path) - it terminated while the L6 splashscreen was still loading.
I remember from many months ago that you wrote about an error in Procdump 7 preventing it from working with Logos, so I tried the old version Procdump 6.0 that successfully captured dumps in November 2013 - however it didn't like the parameters and wanted an additional 1 in between:
but this as well loaded L6 but terminated before any action:
So I'd like to help with a crash dump, you just need to tell me how (or just have it fixed with the new beta, like last time)
Have joy in the Lord!
0
