logos 5 crash...
I have just upgraded to Logos 5 and when I press the icon it begins as normal, but instead of opening it just stops without any error message or anything - as if there is no program???
Comments
-
We need logs, Jack. Read http://wiki.logos.com/Diagnostic_Logging and upload logos.log and any crash logs.
Dave
===Windows 11 & Android 13
0 -
I tried to hold down the ctrl key while opening logos 5, but with no result. Most of the rest on that page is hard to understand, at least for me.
0 -
Now I got in to 'sign in' and I tried, but then the windows told me, that Logos 5 just stopped working and nothing else and it didn't matter if I tried over the internet or offline.
0 -
now I got a crashlog, but when I try to attach it, this below is shown: (is that usefull?)
0 -
There should be a crash log in documents\Logos Log Files; try to upload that. Otherwise contact Logos Support in the morning.
Dave
===Windows 11 & Android 13
0 -
Jack Nørdam said:
now I got a crashlog, but when I try to attach it, this below is shown: (is that usefull?)
yes. it shows that something is duplicate
Error ID: 759
Error detail: ArgumentException: An item with the same key has already been added.Maybe log-reading wizards or developers can use the rest in the log to find out what this item was and how to proceed (e.g. delete a certain file that L5 will automatically re-create).Even better would be a Logos Log that details all the steps the system takes before crashing.
Have joy in the Lord!
0 -
Jack Nørdam said:
now I got a crashlog, but when I try to attach it, this below is shown: (is that usefull?)
Yes, it was. The crash is the same as another that came up earlier, but it needs input from Logos Support to resolve.
Dave
===Windows 11 & Android 13
0 -
so I have to report this to logos support as email
0 -
Jack Nørdam said:
so I have to report this to logos support as email
not necessarily - I'd assume Bradley will pick it up here and either know the answer or point it forward, but even he seems to need a couple hours for sleep every other day or so. If you report it by mail, maybe it helps to include a reference to this thread.
Have joy in the Lord!
0 -
Unfortunately, this looks like a WPF bug (and one that was introduced in WPF 4). I haven't been able to find any information from Microsoft on whether there is a fix or a workaround.
It's crashing when it's loading the list of fonts on your system. More specifically, one of your fonts appears to have two font names in the same language. WPF isn't expecting this, and so it crashes. This could probably be solved by uninstalling that font, but I don't know if we can tell which font it is.
0 -
If that is true - why didn't Logos 4 crash? It was very stable.
0 -
If noone can solve this, can I then uninstall Logos 5 and get my money back, that way I at least have Logos 4, and it works fine?
0 -
I experienced this yesterday. I found a bad registry key...used CCleaner to delete it...works fine now.
0 -
EDIT: The most common font that causes this crash is "DiagramTTBlindAll". If you find this font in your Windows Fonts folder, delete it, then restart Logos 5. If it still crashes, follow the instructions below to identify the incompatible font.
(Logos 5.0 SR-4 will be released soon and will contain a fix for this incompatibility.)
Jack Nørdam said:If that is true - why didn't Logos 4 crash? It was very stable.
Logos 4 used WPF 3.5, which didn't have this bug. It's a new one Microsoft introduced in WPF 4 and that we didn't encounter in beta testing. [:(]
However, I have an idea. Please download LINQPad here ("for .NET Framework 4.x" link in upper right): http://www.linqpad.net/
Download the attached file and unzip it. 1447.WPF Font Crash.zip
In LINQPad, choose File > Open and open the file you unzipped. Press F5 to run it. It should identify the font(s) with the problems. (If it doesn't seem to work please paste its output or a screenshot here.)
Until Microsoft announces a fix for this bug, I think you will have to uninstall those font(s) in order to run Logos 5.
0 -
Jack Nørdam said:
If that is true - why didn't Logos 4 crash? It was very stable.
Logos 4 used .NET Framework 3.5 and WPF 3.5 while Logos 5 uses .NET Framework 4.5 and WPF 4.
Windows 7 has a Fonts folder C:\Windows\Fonts, which has an option to add Family as a column in Details view:
Wonder if same Family is in two Fonts ?
Keep Smiling [:)]
0 -
I got this message Bradley:
Error DiagramTTBlindAll Finished Checked all fonts So, what can I do with that?
0 -
Oh, I deleated the font, and now it seems to work - thanks
0 -
Jack Nørdam said:
So, what can I do with that?
Unfortunately, the script I sent you can't display the name, because getting the name triggers the bug in WPF and causes the crash. However, it's likely that the font in question is named "Diagram something" or "Diagram Blind something".
Open C:\Windows\Fonts in Windows Explorer and look for a font with that name. You can type "diagram" in the "Search fonts" box in the upper right to filter the list. If there's only one font shown, it's probably the one. Otherwise, look through the list for one that most closely matches "DiagramTTBlindAll". When you find it, right-click it and delete it.
Then go back to LINQPad and press F5 again. If the "Error" message still displays, that wasn't the right font. But hopefully, "Error" no longer displays and all the remaining fonts are compatible with Logos 5. If so, Logos 5 should run without crashing.
0 -
Just to confirm, when I deleted the font identified, my copy of Logos 5 started working, also. One question though, I don't seem to see all the tools listed. Are these part of the 1.8GB download that is going on now?
Thanks for the help Bradley and Jack!
0 -
Michael Kahler said:
One question though, I don't seem to see all the tools listed. Are these part of the 1.8GB download that is going on now?
Yes, once Logos 5 installs, it will download all the new databases required by the new Logos 5 features.
0 -
Thank you, Bradley!
0 -
This was quite helpful. I have been experiencing the same crash for many days -- and on more than one machine. Temporarily deleting DiagramTTBlindAll solved the issue.
DiagramTTBlindAll is a widely used chess font; it is used by the super-popular "ChessBase" brand software in particular. I am a little amazed that this slipped past beta testing.
May I suggest that your telephone technical support staff be made aware of this issue.
I spent two hours on the phone on Friday with one of your support staff, and while he was very polite, he was unable to help me, other than to suggest that my version of Windows was bad. (I notice the date of your post is Saturday, which perhaps explains why he did not know of the problem.)
I sincerely believe that the staff member I spoke with was trying his best to help me, and I do appreciate that -- but in the end, he made it clear that it was entirely my problem (and my lost money) if the software crashed. I have to say that I had hoped for better.
Until this incident, I have been an avid Logos user, and my enthusiasm about the program has led to at least two dozen people purchasing Logos. Again, I had hoped for better.
I do want to thank Bradley Grainger for this helpful post, and I eagerly await SR-4.
0 -
I also use Chessbase software and had this same problem. I deleted the DiagramTTBlindAll font and only then could I get Logos 5 to run. I am very relieved to have got Logos 5 up and running, but do hope this doesn't affect my other software.
Shalom and blessings,
Michael
0 -
This issue will be fixed in 5.0 SR-4. You should be able to re-install the DiagramTTBlindAll font and not cause Logos to crash.
Please let us know if you continue to see this crash after 5.0 SR-4 ships.
0 -
Doug Tygar said:
May I suggest that your telephone technical support staff be made aware of this issue.
I spent two hours on the phone on Friday with one of your support staff, and while he was very polite, he was unable to help me, other than to suggest that my version of Windows was bad. (I notice the date of your post is Saturday, which perhaps explains why he did not know of the problem.)
I sincerely believe that the staff member I spoke with was trying his best to help me, and I do appreciate that -- but in the end, he made it clear that it was entirely my problem (and my lost money) if the software crashed. I have to say that I had hoped for better.
Until this incident, I have been an avid Logos user, and my enthusiasm about the program has led to at least two dozen people purchasing Logos. Again, I had hoped for better.
We didn't discover this problem (and the workaround) until Saturday morning, so unfortunately our support staff didn't know how to solve it on Friday.
I'm sorry for your poor experience with support; we want to provide amazing service, and I'm sorry that we didn't deliver on this occasion. I'll pass your feedback on to the CS manager.
0 -
For anyone who's interested (in the very technical details), I've blogged about this crash and how we implemented a workaround: http://code.logos.com/blog/2012/11/how-to-crash-many-wpf-applications-wpf-4-edition.html
0 -
Bradley Grainger (Logos) said:
For anyone who's interested (in the very technical details), I've blogged about this crash and how we implemented a workaround: http://code.logos.com/blog/2012/11/how-to-crash-many-wpf-applications-wpf-4-edition.html
It's fortunate for all that you could implement a workaround (I would hate to be a developer under these circumstances).
Dave
===Windows 11 & Android 13
0 -
Hi Brisa,
FYI - I have installed SR-4 and re-installed the DiagramTTBlindAll font. Everything is now fine - no more crashes.
Thank you all for your help!!
Michael
0 -
thats good, I really love my chess game too.
0
