CRASH: 5.0aB2 Regular Crashing when Mouseovering NA27 w. GRAMCORD with McReynolds Int.
Continuation of thread http://community.logos.com/forums/t/60098.aspx (whose title I can't update).
So there is something about the contents of one layout that seems to trigger the crashes, but another, simpler one does not. The crash-prone layout has a fair number of tabs open (see Screenshot 1) and the second is much simpler.
See the other thread for crash logs.
Thanks
Richard
Screenshot 1 (crashing)
Screenshot 2 (no crashes so far)
Comments
OK thanks will do.
UPDATE: Just triggered it twice there when mouseovering NA27 - log attached. Yep this is looking quite reproducible now ... it's NA27. I've highlighted the rough area that I was mouseovering when crash occurred.
Please note that the "conjunction, coordinating, copulative" popup is "always on top" and is superimposed on all other open Windows (outside L5) - I haven't dismissed the crashed L5 yet.
UPDATE: have tried a number of other Greek NTs but have not yet triggered the crash. The one that I'm viewing when crashing occurs is:
LLS:1.0.317
2009-10-26T18:11:47Z
NA27INT.logos4
I can't reproduce the crash with any other GNT, whether Inline is off or on, and whether Visual Filters are active or not.
how can you tell it's a mouseover by the way?
Looking at the stack trace in the error logs and having a guess [:)] it goes from the function that actually caused the crash down through the stack (each one having been called by the one on the next line). Even without knowing how the code works the function names give you the gist of what's going on...
If you have a look about a third of the way down the stack trace in LogosError.log and work up you can see this:
OnMouseOverSomething —> RaiseActionEventAt —> RaiseDisplayAction .... ShowInformation —> ShowInformationStatusBar
I think the actual crash happens when it tries to load the info to show in the popup (I presume the parsing info popup) and the object its trying to extract the info from isn't there for some reason...