Bug: Repeatable Crash with "Unnamed Collection"
This crash is repeatable. Open up Collections in a floating window or as a tab. Remove the text "Unnamed Collection" and close the window. My Logos 4.2 crashes every time I do this.
I've attached my log file
From Windows 7:
Problem Event Name: CLR20r3
Problem Signature 01: logos4.exe
Problem Signature 02: 4.20.4.8289
Problem Signature 03: 4d069922
Problem Signature 04: Libronix.Utility.ViewModels
Problem Signature 05: 4.20.4.8289
Problem Signature 06: 4d069866
Problem Signature 07: 22c
Problem Signature 08: 18
Problem Signature 09: System.ObjectDisposedException
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Comments
-
If I understood you correctly, I cannot reproduce this problem. Would you mind rebooting then trying again to see if the problem persists?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:
If I understood you correctly, I cannot reproduce this problem. Would you mind rebooting then trying again to see if the problem persists?
Mark,
I will check that computer again when I get home. However, I can repeat this crash on another computer. From Tools, I select Collections. this will open up the window as shown below:
When I remove the default text name of this collection (i.e. remove the text "Unnamed Collection" and leave that box blank), and then close out the Collections window, Logos 4.2 crashes. Hope this clarifies.
David
0 -
David L Bailey said:
Hope this clarifies.
That is what I also did. Unfortunately I am now having other problems with my collections (they have all disappeared) so that may have affected my result. If I had some it might have behaved differently.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
David
I have followed your steps but don't get the crash - I am running the beta version of 4.2a
Graham
0 -
Graham Criddle said:
David
I have followed your steps but don't get the crash - I am running the beta version of 4.2a
Graham
Hello Graham,
thank you for checking. I guess this is an isolated case.The two L4 instances I have on my computers are not copies. That is, each copy of L4 were installed independently.
David
0 -
Mark A. Smith said:David L Bailey said:
Hope this clarifies.
That is what I also did. Unfortunately I am now having other problems with my collections (they have all disappeared) so that may have affected my result. If I had some it might have behaved differently.
Mark,
thanks for checking again. I hope you can get your collections back. Didn't you have Collection issue before?
David
0 -
Just wondering. When you view your set of collections, is one of them called unnamed collection? I always have one, even after I delete it. Is this normal?
thanks,
David
0 -
David L Bailey said:
Just wondering. When you view your set of collections, is one of them called unnamed collection?
Hi David
This was introduced in 4.2 - see http://community.logos.com/forums/p/26852/200774.aspx and http://community.logos.com/forums/t/25901.aspx for discussions of this. You will see that this change hasn't met with universal approval!
Graham
0 -
David L Bailey said:
Just wondering. When you view your set of collections, is one of them called unnamed collection?
If this was the one automatically created when opening Collections from the menu it might behave differently to the one created via the New button, which i could not get to crash. I've created a wiki bug report for this.
Dave
===Windows 11 & Android 13
0 -
Graham Criddle said:
This was introduced in 4.2 - see http://community.logos.com/forums/p/26852/200774.aspx and http://community.logos.com/forums/t/25901.aspx for discussions of this. You will see that this change hasn't met with universal approval!
Thankfully, I don't get this for my Collections which are saved in a Layout - I don't need to access Collections via the menu!
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I've created a wiki bug report for this.
Thank you, Dave, for the wiki bug report.
0 -
David L Bailey said:Dave Hooton said:
I've created a wiki bug report for this.
Thank you, Dave, for the wiki bug report.
Although we could not reproduce this in-house, we believe a fix for this error was included in 4.2a (Beta 5). Let us know if the problem is not resolved in 4.2a.
0
