Crashes more frequent in L6?

I know various people have various problems (downloads, freezing, etc). I just wonder whether the common of us have experienced more crashes since installing L6. It does not happen extremely often, but it does happen (1x, 2x/day). This was not a problem I had with L5 before upgrading.

Find more posts tagged with

Comments

Bradley Grainger (Logos)

1-2 crashes a day is definitely far more frequent than we'd like to see. Can you post your log files here? (Even if you haven't enabled logging, crashes should still be recorded to LogosError.log and LogosIndexerError.log.)

Francis

https://community.logos.com/discussion/comment/675665#Comment_675665

1067.LogosError.logThis is an estimate: I am not sure of the actual number of crashes, just that it happens more frequently than it used to and the latest instance just a moment ago.

1004.LogosError.log

Francis

https://community.logos.com/discussion/comment/675667#Comment_675667

Just happened again!

3250.LogosError.log

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/675672#Comment_675672

There aren't any crashes in that log file, which typically means we need to look in Event Viewer. Please run eventvwr.msc; in Windows Logs > Application, look for Errors from .NET Runtime or Application Error.

Pasting the details here (or right-click > Save, then attaching the file) should let us investigate the error in more detail. (We may also need to have you work with tech support to collect a crash dump we can analyse.)

Bootjack

https://community.logos.com/discussion/comment/675718#Comment_675718

I enjoyed my first shutdown today. It's good to see Dictionaries etc being updated but problems that are problems and have been for a long time now are "not" being fixed. One I mentioned here several weeks ago regarding Factbook was said to have been being worked on back then. I still have to question as to what takes three weeks or better to fix a problem like that. Is it actually being worked on or is it something they might even have in the front lines somewhere "to be" address or "fixed?"

Another age old problem is when bringing up a Layout (for instance) we are still getting the old "not responding" in Logos. For sure, I don't have a clue as to writing programs but does it really take this long to fix or is it really being addressed at all. That is my profound question for today! :-)

Francis

https://community.logos.com/discussion/comment/675718#Comment_675718

There aren't any crashes in that log file, which typically means we need to look in Event Viewer. Please run eventvwr.msc; in Windows Logs > Application, look for Errors from .NET Runtime or Application Error.

Pasting the details here (or right-click > Save, then attaching the file) should let us investigate the error in more detail. (We may also need to have you work with tech support to collect a crash dump we can analyse.)

Here are the last two instances:

2210.eventvwr.txt

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/676363#Comment_676363

I'm seeing two types of crashes here.

Does one occur when you try to delete a collection in the Collections tool?

The other looks as though it might occur even when you're not doing anything actively in the program, maybe 2-3 minutes after startup. If that's happening frequently, it would be best to work with Tech Support to collect a crash dump (that we can look at to discover the underlying problem).

Francis

https://community.logos.com/discussion/comment/676470#Comment_676470

I have worked with collections in the last couple days but the crashes have been occurring before that and I have not noticed that it happened particularly when I was working with collections.

I am not sure that the 2-3 minutes after startup criteria fits the experience I recollect either.

Francis

https://community.logos.com/discussion/comment/676473#Comment_676473

I can confirm in the latest crash, which just occurs, that I was not working with collections and it was certainly not early at all after start up (I have been working in L6 for several hours straight). This time it happened just as I highlighted text in the NA28 (but the resource is not the problem since I only acquired this one yesterday).

1157.cef.log

4718.LogosError.log

5315.eventvwr.txt