Problems with Logos 4 crashing when coping and pasting
I would hit the copy button in the info window and then go to paste it in the notes then Logos would crash. This is the first I have had this problem and I have Logos 4b. I am going to upload my logs and hopefully I do the correct one. 
Hopefully that is the correct log to post. If not, let me know.
Comments
-
Vickie Weers said:
I would hit the copy button in the info window and then go to paste it in the notes then Logos would crash. This is the first I have had this problem and I have Logos 4b. I am going to upload my logs and hopefully I do the correct one.
Hopefully that is the correct log to post. If not, let me know.
Hi Vickie, there should be another file called Logos4Crash.txt - that is the file we need.
0 -
Doesn't seem to be doing that file. Let me see if I can get the log files to record it again.
0 -
Vickie Weers said:
Doesn't seem to be doing that file. Let me see if I can get the log files to record it again.
In 4.0b it will (almost always) generate a Logos4Crash.txt file if it crashes - maybe it just locked up and didnt crash? Can you be more specific with what you were looking up in the information window and which sections (if not all of them) you copied?
0 -
It crashed alright. because I never had it crash at all before b came out - here is the information from the crash window that popped up in Vista when it crashed.
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos4.exe
Problem Signature 02: 4.2.3.7337
Problem Signature 03: 4b97e7f9
Problem Signature 04: WindowsBase
Problem Signature 05: 3.0.0.0
Problem Signature 06: 498d25be
Problem Signature 07: da
Problem Signature 08: 1b
Problem Signature 09: FatalError
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Does that help? What I was doing was copying some information out of Louw-Nida for a Word and then pasting it directly into the Notes.
0 -
I meant to mention. If I copy and paste directly from that resource and not the information window then it doesn't crash, only when I use the information window tool and click on the copy button - then paste I get this crash.
0 -
Vickie Weers said:
I meant to mention. If I copy and paste directly from that resource and not the information window then it doesn't crash, only when I use the information window tool and click on the copy button - then paste I get this crash.
I still can't reproduce this crash - which word were you looking up? If possible can you reproduce this crash and then post the new log? Maybe you have some specific settings in the Information window that are different from the default? Perhaps a screenshot of the window before you copied would help.
0 -
Let me check. I know I was playing with it after I first got it.
0 -
I have tried to get the log to work. My husband even ran the java script to turn it on. There wasn't a specific word I was doing when I was trying to recreate it. But I will see if it makes a difference. I will try again, recreating the crash. It usually takes several tries before it crashes.
0 -
It seems to be only crashing when I use the Louw-Nida resource. I tried it with the Strongs & TNDT and it worked fine but not the Louw-Nida one. Now if I copy and paste directly from the actual resource it does fine. But when I copy and paste from the Information tool window is when it crashes. All I can get information wise is the this from the window telling me that Logos stopped working:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos4.exe
Problem Signature 02: 4.2.3.7704
Problem Signature 03: 4ba7afea
Problem Signature 04: WindowsBase
Problem Signature 05: 3.0.0.0
Problem Signature 06: 498d25be
Problem Signature 07: da
Problem Signature 08: 1b
Problem Signature 09: FatalError
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
0 -
Vickie Weers said:
It seems to be only crashing when I use the Louw-Nida resource. I tried it with the Strongs & TNDT and it worked fine but not the Louw-Nida one. Now if I copy and paste directly from the actual resource it does fine. But when I copy and paste from the Information tool window is when it crashes. All I can get information wise is the this from the window telling me that Logos stopped working:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos4.exe
Problem Signature 02: 4.2.3.7704
Problem Signature 03: 4ba7afea
Problem Signature 04: WindowsBase
Problem Signature 05: 3.0.0.0
Problem Signature 06: 498d25be
Problem Signature 07: da
Problem Signature 08: 1b
Problem Signature 09: FatalError
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
So there is no Logos4Crash.txt file? The new feature in 4.0b is that a crash will generate that file, but that makes me think the problem is deeper and is preventing L4 from even generating debugging information.. Please post the new Logos4.log file directly following the crash incase it actually wrote the crash information this time. I will provide this log to the development team and maybe they can provide more insight. Thanks.
0 -
OKay, I will do that. Let me recreate a crash and then I will upload it.
0 -
Here it is and here is the specific reference I was copy and pasting if it helps.
Louw Nida 7.45 7.45 στῦλοςa, ου m: an upright shaft or structure used as a building support—‘pillar, column.’ ποιήσω αὐτὸν στῦλον ἐν τῷ ναῷ τοῦ θεοῦ μου ‘I will make him a pillar in the sanctuary of my God’ Re 3:12. στῦλος is also used in speaking of the leaders of the Jerusalem church (Ga 2:9; see 36.7). In Ga 2:9 the focus is upon the important role of such persons in supporting and maintaining the church. In a number of languages such a figurative meaning may be expressed as ‘very important persons in the church.’ In a number of languages pillars may be described as ‘those poles which support the house’ or ‘those logs which hold up the roof.’ Usually, however, there are rather specific terms to designate these important parts in the construction of houses or halls.
0 -
Thank you I was able to reproduce the crash, I will let you know when this gets fixed.
0 -
Thanks, George. I appreciate it.
0 -
This crash will be fixed in 4.0c, which is currently in beta testing.
Melissa
0
