Logos 4 Crashing Even More since update 4.6 (4.60.0.2972)

I've been experiencing crashes before but now it often can't stay open more than a few minutes without crashing and I don't do anything. I do have about 20-30 tabs going, which is quite typical for my research, but haven't had the problem until the last several updates, but now with the most recent update it just keeps crashing within minutes. According to the windows report on the crash it lists this:

Description

Stopped working

Faulting Application Path: C:\Users\Tony\AppData\Local\Logos4\System\Logos4.exe

Problem signature

Problem Event Name: CLR20r3

Problem Signature 01: logos4.exe

Problem Signature 02: 4.60.0.2972

Problem Signature 03: 503d41d1

Problem Signature 04: mscorlib

Problem Signature 05: 2.0.0.0

Problem Signature 06: 4ef6c7cc

Problem Signature 07: 1ec

Problem Signature 08: 0

Problem Signature 09: System.OutOfMemoryException

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 5129

Extra information about the problem

Bucket ID: 3229854538

0523.Logos4LogFiles.zip

Find more posts tagged with

Comments

MJ. Smith

Does it crash less often if you have fewer panes open? It looks like a simple out of memory condition. If others have similar problems, I'd suspect a memory link.

DMB

https://community.logos.com/discussion/comment/393533#Comment_393533

MJ's answer illustrates how the brain (apparently) stores information or at least how it retreives it. But I was suspecting the same thing .... but not Logos ... some other process is chewing up memory. I had that problem in W7/32 last year and it was a Windows process that the web said wasn't needed. And it wasn't.

EDIT: It took me several minutes to write the above two sentences. I don't know why Logos-related products have so much problem with text/keyboard linking (leaking).

Tony Nunez

https://community.logos.com/discussion/comment/393533#Comment_393533

Yes it still crashes when I've reduced the number of tabs by half. From what I gather, it appears to be a 'memory leak' made worse by operating a 32-bit built app (Logos 4) on a 64 bit system. Apparently, if it is a memory leak the frequency of these crashes will increase. If this is correct how do I resolve this? thanks!

Dave Hooton

https://community.logos.com/discussion/comment/393688#Comment_393688

A program rarely crashes with a memory leak - look at Task Manager to see how much is being used. Is the working set memory over 300MB? We need to see some logs to confirm the issue, but it usually means that there is none available out of the max. 2 GB allocated to a 32-bitprogram.

Tony Nunez

https://community.logos.com/discussion/comment/393689#Comment_393689

Logs already attached in the first post. Unless I did something wrong. thanks.

And what is a "working set" and how do I set it? thanks.

Here's the reference to where I got my thoughts from my previous post: http://community.logos.com/forums/p/53668/391431.aspx#391431

Lynden O. Williams

https://community.logos.com/discussion/comment/393690#Comment_393690

Tony, based on what I am seeing, 8GB of Ram, you should have plenty left. I am running L4 on a 64bit Windows 7 platform with 4GB of Ram, and it seldom uses more than 250-300 MB of Ram, even with 52 tabs open.

Something else is going on. Follow the instructions here http://wiki.logos.com/Diagnostic_Logging to upload detailed logos so that others can trouble shoot the problem.

Tony Nunez

https://community.logos.com/discussion/comment/393696#Comment_393696

Is my log files attached in my first post inadequate?

Lynden O. Williams

https://community.logos.com/discussion/comment/393697#Comment_393697

Is my log files attached in my first post inadequate?

Sorry, I did not see zipped files. I am not good at reading them. Make sure that you upload the Logos crash log, logos error log, and the Logos 4 log.

Tony Nunez

https://community.logos.com/discussion/comment/393700#Comment_393700

Yes, all included in the one zipped file.

Dave Hooton

https://community.logos.com/discussion/comment/393690#Comment_393690

Logs already attached in the first post.

Sorry - missed them.

The problem is with Sentence Diagrams. Try holding the CTRL key whilst starting Logos4 and selecting Blank Layout. The problem may lie with a particular diagram, and you'll know which one when trying to open it! Or it may be the number of diagrams being opened in your Layout.

And what is a "working set" and how do I set it? thanks.

Task Manager has a number of ways to show memory used on the Processes tab. One heading is Working Set. If not shown you can select it from the View menu.

Tony Nunez

https://community.logos.com/discussion/comment/393746#Comment_393746

I do use a large sentence diagram for my research (I use it to create block diagrams). Currently am block diagramming the entirety of 1 Peter.

How do I fix this block diagram?

How do I avoid the problem in the future?

I've found the "working set" (using Process Hacker) but what should I look for?

And yes it shows Logos using more than 300 MB (about the 340 MB range). Oh, and it just crashed again when it popped up all of a sudden to 510 MB while I was writing this reply so I wasn't doing anything on Logos.

How do I set it?

What am I to look for exactly and do about it?

Is the solution downgrading my OS to a 32 bit system?

Thanks heaps!

Dave Hooton

https://community.logos.com/discussion/comment/393690#Comment_393690

Here's the reference to where I got my thoughts from my previous post: http://community.logos.com/forums/p/53668/391431.aspx#391431

Yes, but there is no reference to memory leaks. "out of memory" literally means there is no more memory that can be allocated to the program when it is limited to a max. 2 GB by the OS.

Dave Hooton

https://community.logos.com/discussion/comment/393748#Comment_393748

I do use a large sentence diagram for my research (I use it to create block diagrams). Currently am block diagramming the entirety of 1 Peter.

How do I fix this block diagram?

You may have to split it into 2 or more diagrams. If you can open it from a Blank Layout you can proceed from there, else you'll have to Delete it and start from scratch.

I've found the "working set" (using Process Hacker) but what should I look for?

How do I set it?

What am I to look for exactly and do about it?

This is rather moot as we have identified the cause. It only states the amount of memory being used. If not visible go to the View menu and select it from Select Columns..

Tony Nunez

https://community.logos.com/discussion/comment/393751#Comment_393751

You may have to split it into 2 or more diagrams. If you can open it from a Blank Layout you can proceed from there, else you'll have to Delete it and start from scratch.

I've done way too much work on this block diagram and didn't know there was some kind of limitation on text length.

What exactly is the problem? Is it that I have the block diagram open along with too many other tabs open? Is there some kind of bug in the block diagram? How do I create them to avoid this in the future? How do I know when its too long? It seems that if it crashes its too late. If this is a problem why doesn't Logos make a text length limitation on these sentence diagrams to avoid memory problems?

If I must break the diagram down into segments, is there an efficient way of doing this without having to manually start from scratch? It seems copy and paste only copy and pastes the whole diagram and I can't seem to figure out a way to delete text.

Thanks for your help. Many work hours are at stake here.

Dave Hooton

https://community.logos.com/discussion/comment/393752#Comment_393752

I've done way too much work on this block diagram and didn't know there was some kind of limitation on text length.

I don't use this feature but there isn't a limit set by the program, as with other documents. Working with large documents will affect response times and there is always the risk that a large number of open, large and/or small, documents will impact OS memory limits. You can only manage that as I described.

A quick scan of posts shows that chapter length Diagrams are handled OK.

If I must break the diagram down into segments, is there an efficient way of doing this without having to manually start from scratch?

Hopefully others can contribute here.

Tony Nunez

https://community.logos.com/discussion/comment/393760#Comment_393760

I've experimented with having Logos open with the block diagram open in a tab and without. Its not the block diagram per se that's causing the crashing of Logos. I've monitored Logos' working set using Process Hacker. It usually sits around the 240-340 MB range but after a while (usually within 10-15 mins.) it will hike up to 400+MB and if I don't force a reducing of the working set (via Process Hacker) it will spike up to over 500MB and when it does it crashes every time!

I rely so much on Logos for my work. I can't have it crash every 10-15 minutes. I really need a fix. Please help. Should I call Logos?

Is there a patch or something... maybe an app... that can just automatically conduct a reduce working set command when it gets up to 450 MB?

Thanks!

Dave Hooton

https://community.logos.com/discussion/comment/394624#Comment_394624

Should I call Logos?

Yes. They can remotely logon to your computer and try to diagnose the issue.

Hunter Clagett

https://community.logos.com/discussion/comment/394624#Comment_394624

Give us a call at 1-800-875-6467 Mon-Fri from 6 am to 5 pm PST.

Thanks,

Tony Nunez

https://community.logos.com/discussion/comment/395090#Comment_395090

Just an update for any out there who may be experiencing the same problem...

I called Logos and got great help! Here's what they had me do:

1) Open File Location - with Logos not running, right click on app icon and click "open file location"

2) Rename "Documents" folder (e.g. Documents1)

3) Run Logos - it will sync with their servers and create a new "Documents" folder

Apparently there was either a memory leak, bug, or file corruption with my sentence diagram and syncing with Logos servers can sometimes fix the problem.

It worked. BUT not long after doing further modifications of the sentence diagram it was back to the old crashing problem.

They advised me to call back if this were to happen.

I've attached the log files.

I'll let ya'll know what happens.

5710.Logos4LogFiles2.zip