Had several panels open along with a Passage guide and Exegetical guide. Clicked on the BDAG hyperlink in the Exegetical guide and crashed.
5633.LogosCrash.txt
Thanks for posting the logs. This problem should be fixed in 5.0b beta 2 when it ships.Regards,
Seth Copeland Logos SW Developer
Thanks Seth
Seth,
Does this include ALL the other occurrences of Error 1887 since the beta was released?
Seth, Does this include ALL the other occurrences of Error 1887 since the beta was released?
If so, that would be great news[:)]
I would hope so[:S]
Seth, Does this include ALL the other occurrences of Error 1887 since the beta was released? If so, that would be great news
If so, that would be great news
Looking forward to it [Y][H]
I'm not sure if it will fix all instances of Error 1887, if that simply corresponds to a null reference exception. It should fix all the crashes occurring that have a stack trace that looks like this though.
System.NullReferenceException: Object reference not set to an instance of an object. at Libronix.Utility.Data.DataReaderUtility.CastValue[T](Object value) at Libronix.Utility.Data.Connector.ExecuteScalar[T](String strText, Object[] aobjParameterNamesAndValues) at Libronix.Utility.Data.PoolableConnector.ExecuteScalar[T](String strText, Object[] aobjParameterNamesAndValues) at Libronix.DigitalLibrary.HistoryManager.<DoUpdateLastVisitedWork>d__17.MoveNext()
Regards,
Seth
Thanks, Seth. The History Manager cases were the ones of concern.
Has anyone confirmed that this bug has indeed been fixed? I'm going through collecting links to threads with bug reports in 5.0b that have not been resolved yet.
There have been so many reports of error 1887 History Manager in so many circumstances - and typically there wasn't a real "do these three steps and it will crash" replication pattern - more like "do this what normally works fine, and you'll have a good chance of a crash". Such as opening a Community Note I had created myself some seconds ago. I can say that I had them a lot, and don't see any of them lately (from beta 3, I think), so for me it's fixed.
I'd say it is fixed - I haven't crashed with it nor seen any reports of the crash since beta 2.
