Crash when opening additional resources 6.8 B1
When I'm in a saved layout that contains the Info pane and click on the "+" symbol on a pane to add a resource, there's a momentary pause then a crash. If I remove and re-add the Info pane to any layout, I no longer crash through clicking the "+" symbol. I have a sampling of logs during the crash when I had removed all other panes except for ESV and Info.
BTW, the paperclip insertion isn't working for me so I'm trying to share a link via dropbox.
Comments
-
Reuben Helmuth said:
When I'm in a saved layout that contains the Info pane and click on the "+" symbol on a pane to add a resource, there's a momentary pause then a crash. If I remove and re-add the Info pane to any layout, I no longer crash through clicking the "+" symbol. I have a sampling of logs during the crash when I had removed all other panes except for ESV and Info.
BTW, the paperclip insertion isn't working for me so I'm trying to share a link via dropbox.
That's... a very strange log error. Is the layout one you've had for a long time? My initial hunch (I'm not a developer) is that this is from before we redid the Info panel a few releases ago and something was saved funny. The specific issue seems to be a matrix with boundaries that aren't numbers, which is... odd.
If you open the layout, save it as a new one (identical panels), and then load to that, does it reproduce with the same steps?
In the meantime, I'll pass these logs on to a developer to investigate.
0 -
Dylan Rondeau said:
If you open the layout, save it as a new one (identical panels), and then load to that, does it reproduce with the same steps?
Yes, I have the same results. I also tried removing and re-adding the info panel and saving the layout, but still crashed is I loaded to it and tried adding a resource.
0 -
OK!.....This is gonna sound crazy!
I think I've narrowed down the source of the error significantly... The crash seems to only occur when the Info panel is in one of the narrow (non-resizable) panes on the left or right of the main window...BUT only if the "Reading Lists" panel occupied that same pane BEFORE the Info panel arrived. The Reading Lists panel does not necessarily have to still be present, it must simply arrive prior to the Info panel's arrival.
To test this, simply open a Bible, open the Reading Lists tool (let it simply default to the left narrow pane) then open the Info panel and drag it into that left narrow pane. Now you can either leave the Reading list tool or close it then click the "+" symbol on the pane that contains the bible. Bingo!, you should successfully have crashed Logos!😜
Hopefully this helps nail'm!
0 -
Argh! I'm finding a hundred and one ways to trigger this crash (consistently)! It's not just the info panel/reading lists panel interaction.😟😠😖😖😭😭
0 -
-
-
Reuben Helmuth said:
BUMP @Dylan Rondeau
I did create a case, sorry for not stating that explicitly and for my delay in responding.
Thus far we're unable to reproduce the issue. Could you record a screencast for us, so we can see your exact layout and how the app is behaving? If you don't have it already, Jing is a free screenshot/screencast tool: https://www.techsmith.com/jing.html
My apologies again for your frustration, and thanks for helping us track this down.
0 -
Dylan Rondeau said:
Thus far we're unable to reproduce the issue. Could you record a screencast for us, so we can see your exact layout and how the app is behaving?
Thanks for your response Dylan.
I am now thoroughly perplexed... The crash was still occurring a couple days ago (after carefully ascertaining that I was on beta 3), and with a remarkable degree of "dependability"! From what I could tell it always involved the non-resizable side panes, and generally if a tab had been dragged to the opposite side of the screen (into the other non-resizable pane).
...that said...when I went to get a screencast for you this evening, I was unable to crash it using the "+" symbol as before. Logos still crashes for me intermittently, but seemingly randomly (except that it's usually when I swipe over to a different "desktop" (OS X)). I even went back to the identical layout where I discovered the crash, but was unable to reproduce it. The reason this baffles me is that (to my knowledge) no engine update was pushed to me since I last was consistently crashing. In my effort to narrow down the possibilities I probably crashed 30-40 times!, and now...nothing! Hopefully the bug died and didn't simply morph! 😳😆
0
