-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resizing Analysis Window Causes Crash #535
Comments
I just reproduced this in MacOS.
I upgraded to QRiS 1.0.7 and the same problem occurs. Note that I can undock the project explorer dockable widget and it doesn't crash QGIS. |
This is an odd one - not quite sure how to debug the qt widget and catch the error. I have also reproduced this error. It seems if you resize the Analysis panel (i.e. make it taller) before undocking, QGIS does not crash. |
Given that the project explorer (and other QRiS) widgets don't crash, it tells me that one or more widgets on this dockable window are not being created properly. A few things to try:
|
@philipbaileynar @KellyMWhitehead Just wanted to add a little more info on this. Its been an issue for a while, I should have posted something sooner... The crash only happens if you immediately undock/resize upon opening widget. It seems it needs to think for a minute. If you give it 10-15 seconds after opening before doing anything it doesn't crash. |
This still a bit of a flakey crash that is hard to reproduce. I was able to get the error to show up when 1) the analysis had metric values and 2) I tried to move the window right away after it appeared. My guess is that the form is still loading the metric values and building the table when the user attempts to move it. I was able to change the order of operations when creating the dockable analysis window that seems to have fixed the issue for me. Please test in the upcoming 1.0.8 release and let me know if this shows up again. |
From Luke Worshom via FreshDesk:
https://riverscapes.freshdesk.com/a/tickets/194
The text was updated successfully, but these errors were encountered: